Paraşüt integration
Connects contacts, invoices, payments and products to an accounting assistant.
The Paraşüt connection provides a controlled access layer for contact search, balances, sales and purchase invoices, products and sales-invoice PDF download. During initial use, the team should record the source of the question, applied filters and any confirmation step. That trace makes it visible that the connection is being used with the right scope in daily work.
Connector facts
- Availability
- self_hosted
- Authentication
- bearer
- Domain
- erp
Data surface and the business question
The Paraşüt connection is designed for contact search, balances, sales and purchase invoices, products and sales-invoice PDF download. Connects contacts, invoices, payments and products to an accounting assistant. That means an assistant uses the permitted live-system context instead of guessing from a document. The result still depends on the freshness of the source system and the permissions granted to the connection.
A useful request makes clear which record is needed for which team. For this connection, a reliable flow is first locating the customer or invoice, then narrowing the balance, due-date or unpaid-invoice question. This makes filters and source records easier to inspect than asking for a broad list to be summarised.
Permissions, confirmation and responsibility
write calls such as issuing an invoice, recording a payment or editing a contact do not complete without single-use user confirmation. This is more than a technical detail: an incorrect action in a financial, customer, production or legal record can have real consequences. Reading a result and changing an external system are not the same level of authority.
Before rollout, decide which assistants and departments can see this data. If a result is unexpectedly broad, reduce the access scope; if data is absent, do not let the assistant invent the missing record. The underlying system record and the accountable owner remain the final check for every consequential result.
Setup and operational review
runs on a self-hosted mcp-host with a bearer token and is visible only to the assistant it is attached to. At setup, use a separate connection identity with least privilege so the accessible data does not exceed the operational need. For OAuth connections review the consent screen; for bearer connections review token scope, storage and ownership with the responsible team.
10 read-only and 10 confirmation-gated write tools. This statement comes from the catalog or tool definition; no extra count is invented for a vendor-managed changing surface. During a pilot, observe real questions, returned records, confirmation steps and unnecessary calls. That evidence makes cost visible and exposes over-broad permissions early.
Frequently asked questions
What can this connection query?
contact search, balances, sales and purchase invoices, products and sales-invoice PDF download
What is a reliable working flow?
first locating the customer or invoice, then narrowing the balance, due-date or unpaid-invoice question
Are write operations unrestricted?
write calls such as issuing an invoice, recording a payment or editing a contact do not complete without single-use user confirmation
How is the connection set up?
runs on a self-hosted mcp-host with a bearer token and is visible only to the assistant it is attached to
Which metric is verifiable?
10 read-only and 10 confirmation-gated write tools
What should I do with the result?
Review the result against the relevant system record and company policy; an assistant response does not replace an authorised person’s decision.