AGENT SKILL

pm-visma-economic

Visma e-conomic connector knowledge and safe action guide.

License 许可
AGPL-3.0
所属仓库
polymetrics-ai/cli
最近更新
2026-09-21
Stars
★ 7
Forks
0

01 前言 Front Matter

name
pm-visma-economic
description
Visma e-conomic connector knowledge and safe action guide.

02 资源文件 1

03 SKILL.md 正文

pm-visma-economic

Purpose

Reads customers, suppliers, products, invoices, orders, quotes, departments, payment terms, units, and accounts from the Visma e-conomic REST API, and writes customers, suppliers, products, units, and payment terms.

Icon

Capabilities

  • check=true catalog=true read=true write=true query=false
  • Integration type: api

Authentication

  • Use pm credentials add with --from-env or --value-stdin for secret fields.

Configuration

  • base_url
  • start_date
  • agreement_grant_token (secret) (required)
  • app_secret_token (secret) (required)

ETL Streams

  • customers:
    • primary key: id
    • fields: currency(string), id(string), name(string)
  • suppliers:
    • primary key: id
    • cursor: lastUpdated
    • fields: address(string), balance(number), city(string), corporateIdentificationNumber(string), country(string), currency(string), ean(string), email(string), id(integer), lastUpdated(string), name(string), telephoneAndFaxNumber(string), vatNumber(string), zip(string)
  • products:
    • primary key: id
    • cursor: lastUpdated
    • fields: barred(boolean), costPrice(number), description(string), id(string), lastUpdated(string), name(string), salesPrice(number)
  • invoices_booked:
    • primary key: id
    • cursor: lastUpdated
    • fields: currency(string), date(string), dueDate(string), grossAmount(number), id(integer), lastUpdated(string), netAmount(number), paymentTerms(object), vatAmount(number)
  • invoices_drafts:
    • primary key: id
    • cursor: lastUpdated
    • fields: currency(string), date(string), dueDate(string), grossAmount(number), id(integer), lastUpdated(string), netAmount(number), notes(object), paymentTerms(object), references(object), vatAmount(number)
  • orders_drafts:
    • primary key: id
    • cursor: lastUpdated
    • fields: currency(string), date(string), grossAmount(number), id(integer), lastUpdated(string), netAmount(number), notes(object), references(object), vatAmount(number)
  • orders_sent:
    • primary key: id
    • cursor: lastUpdated
    • fields: currency(string), date(string), grossAmount(number), id(integer), lastUpdated(string), netAmount(number), notes(object), references(object), vatAmount(number)
  • quotes_drafts:
    • primary key: id
    • cursor: lastUpdated
    • fields: currency(string), date(string), grossAmount(number), id(integer), lastUpdated(string), netAmount(number), notes(object), references(object), vatAmount(number)
  • quotes_sent:
    • primary key: id
    • cursor: lastUpdated
    • fields: currency(string), date(string), grossAmount(number), id(integer), lastUpdated(string), netAmount(number), notes(object), references(object), vatAmount(number)
  • departments:
    • primary key: id
    • fields: id(integer), name(string)
  • payment_terms:
    • primary key: id
    • fields: duration(integer), id(integer), name(string), paymentTermsType(string)
  • units:
    • primary key: id
    • fields: id(integer), name(string)
  • vat_types:
    • primary key: id
    • fields: accountingApplication(string), id(integer), name(string), vatPercentage(number)
  • vat_zones:
    • primary key: id
    • fields: enabledForCustomer(boolean), enabledForSupplier(boolean), id(integer), name(string)
  • accounts:
    • primary key: id
    • fields: accountType(string), balance(number), blocked(boolean), id(integer), name(string)
  • customer_groups:
    • primary key: id
    • fields: accountNumber(integer), id(integer), name(string)
  • product_groups:
    • primary key: id
    • fields: id(integer), name(string), salesAccount(object)

Sync Modes

  • ETL sync modes: full_refresh_append, full_refresh_overwrite, full_refresh_overwrite_deduped, incremental_append, incremental_append_deduped

Reverse ETL Actions

  • create_customer:
    • endpoint: POST /customers
    • required fields: name, currency, paymentTerms, customerGroup, vatZone
    • risk: external mutation; approval required
  • update_customer:
    • endpoint: PUT /customers/{{ record.id }}
    • required fields: id, name, currency, paymentTerms, customerGroup, vatZone
    • risk: external mutation; approval required
  • delete_customer:
    • endpoint: DELETE /customers/{{ record.id }}
    • required fields: id
    • risk: destructive external mutation (deletes a customer permanently); approval required
  • create_supplier:
    • endpoint: POST /suppliers
    • required fields: name, currency, paymentTerms, group, vatZone
    • risk: external mutation; approval required
  • update_supplier:
    • endpoint: PUT /suppliers/{{ record.id }}
    • required fields: id, name, currency, paymentTerms, group, vatZone
    • risk: external mutation; approval required
  • delete_supplier:
    • endpoint: DELETE /suppliers/{{ record.id }}
    • required fields: id
    • risk: destructive external mutation (deletes a supplier permanently); approval required
  • create_product:
    • endpoint: POST /products
    • required fields: productNumber, name, salesPrice, productGroup
    • risk: external mutation; approval required
  • update_product:
    • endpoint: PUT /products/{{ record.id }}
    • required fields: id, name, salesPrice, productGroup
    • risk: external mutation; approval required
  • delete_product:
    • endpoint: DELETE /products/{{ record.id }}
    • required fields: id
    • risk: destructive external mutation (deletes a product permanently); approval required
  • create_unit:
    • endpoint: POST /units
    • required fields: name
    • risk: external mutation; approval required
  • update_unit:
    • endpoint: PUT /units/{{ record.id }}
    • required fields: id, name
    • risk: external mutation; approval required
  • delete_unit:
    • endpoint: DELETE /units/{{ record.id }}
    • required fields: id
    • risk: destructive external mutation (deletes a unit permanently); approval required
  • create_payment_term:
    • endpoint: POST /payment-terms
    • required fields: name, paymentTermsType
    • risk: external mutation; approval required
  • update_payment_term:
    • endpoint: PUT /payment-terms/{{ record.id }}
    • required fields: id, name, paymentTermsType
    • risk: external mutation; approval required
  • delete_payment_term:
    • endpoint: DELETE /payment-terms/{{ record.id }}
    • required fields: id
    • risk: destructive external mutation (deletes a payment term permanently); approval required

Security

  • read risk: external Visma e-conomic API read of customer, supplier, product, and accounting data
  • write risk: external mutation of Visma e-conomic customers, suppliers, products, units, and payment terms; approval required
  • approval: read: none; write: required for every action
  • Never pass secret values in chat, shell arguments, logs, docs, or JSON output.

Commands

Inspect as a manual

pm connectors inspect visma-economic

Inspect as structured JSON

pm connectors inspect visma-economic --json

Agent Rules

  • Run pm connectors inspect visma-economic before creating credentials or plans.
  • Use --json only when the caller needs structured output; use the manual for human-readable guidance.
  • Never ask the user to paste secret values into chat.
  • For reverse ETL writes, create a plan, show the preview, wait for explicit approval, then run with the approval token.

04 同仓库更多 Skills