Paraşüt integration | Zervanor
← All connectors

Paraşüt

Also an agent tool
finance-billing

Paraşüt Turkish cloud pre-accounting & e-invoicing integration — JSON:API v4 REST over OAuth2: contacts, products, sales invoices, e-Fatura/e-Arşiv/e-SMM, purchase bills, with polling for new sales invoices.

34 actions · 2 triggers

The Paraşüt integration lets you connect Paraşüt to your automations with 34 actions and 2 triggers — and every action is also a tool an AI agent can call. Examples: Get Me, List Contacts, Get Contact, Create Contact, Update Contact. No blank-canvas wiring — connect it and use it in your workflows.

Every action below is also a tool an AI agent can call — the same pack powers your workflows and your agents.

Triggers 2

Events in Paraşüt that can start a workflow.

webhook

Sales Invoice Created

Fires when a new sales invoice is created (polling list_sales_invoices).

polling

New sales invoice

Fires when a new sales invoice is created in Paraşüt.

Actions 34

What Zervanor can do in Paraşüt.

Sales Invoices9

GET

List Sales Invoices

List sales invoices.

GET

Get Sales Invoice

Show one sales invoice.

POST

Create Sales Invoice

Create a sales invoice (details[] line items link products via relationships).

PUT

Update Sales Invoice

Edit a sales invoice.

DELETE

Delete Sales Invoice

Delete a sales invoice.

POST

Pay Sales Invoice

Record a payment/collection against the invoice.

DELETE

Cancel Sales Invoice

Cancel the invoice.

PATCH

Recover Sales Invoice

Recover a cancelled invoice.

PATCH

Convert Estimate to Invoice

Convert an estimate into a sales invoice.

Contacts5

GET

List Contacts

List contacts (customers/suppliers).

GET

Get Contact

Show one contact.

POST

Create Contact

Create a contact. Minimal attributes: name + account_type (customer|supplier).

PUT

Update Contact

Edit a contact.

DELETE

Delete Contact

Delete a contact (→ 204). Cleanup action for the create_contact write test target.

Products5

GET

List Products

List products.

GET

Get Product

Show one product.

POST

Create Product

Create a product.

PUT

Update Product

Edit a product.

DELETE

Delete Product

Delete a product.

Purchase Bills4

GET

List Purchase Bills

List purchase bills (alış faturaları).

GET

Get Purchase Bill

Show one purchase bill.

POST

Create Purchase Bill

Create a purchase bill (basic or detailed form).

POST

Pay Purchase Bill

Add a payment to a purchase bill.

E Archives3

POST

Create e-Arşiv

Issue an e-Arşiv from a sales invoice (fallback when the buyer is not an e-Fatura user). Async → 201 trackable_job; poll then get_e_archive.

GET

Get e-Arşiv

Show the e-Arşiv (status bounced|sent|printed|legalized).

GET

Get e-Arşiv PDF

Get the e-Arşiv PDF.

E Invoices3

POST

Create e-Fatura

Issue an e-Fatura from a sales invoice (relationships.invoice = sales_invoice id; attributes.to = recipient inbox, scenario basic|commercial). Async → returns 201 trackable_job; poll get_trackable_job then get_e_invoice.

GET

Get e-Fatura

Show the e-Fatura (status waiting|failed|successful).

GET

Get e-Fatura PDF

Get the e-Fatura PDF.

E Smms2

POST

Create e-SMM

Issue an e-SMM (serbest meslek makbuzu / e-Makbuz).

GET

Get e-SMM

Show the e-SMM.

E Invoice Inboxes1

GET

List e-Fatura Inboxes

Look up a recipient's e-Fatura inbox (the 'to' for create_e_invoice). Filter by VKN/TCKN.

Me1

GET

Get Me

Authenticated user profile + accessible companies (discover company_id). GET /v4/me — no company_id needed.

Trackable Jobs1

GET

Get Trackable Job

Poll an async job status (running|done|error) returned by e-document creates.

Automations using Paraşüt

Template

Month End e-Archive Close v2

On the fifth of each month the sales invoices in Parasut are scanned for ones that never had an e-Document issued against them. The owner sees the list before anything happens, and on approval an e-Arsiv is issued through Parasut for each one. Invoices without their e-Document are a quiet compliance debt: the sale is recorded, the tax document is not, and nobody notices until the accountant closes the period.

Template

Overdue Invoice Payment Chase v2

Every morning the open sales invoices in Parasut are scanned for ones past their due date with a balance still outstanding. After the owner approves, each customer gets an SMS reminder. Three days later the same invoices are re-read, and only those still unpaid go to a second approval for a firmer notice. Small businesses lose collectable money simply because nobody has time to run the ladder by hand.

Template

Parasut to Hepsiburada Stock Sync

Each morning the stock counts in Parasut (the source of truth) are compared against the live Hepsiburada listings. Products whose stock differs go to the owner for approval, and on approval the Hepsiburada listings are set to the Parasut value. Tracked products that have no Hepsiburada listing at all are reported. Overselling on a marketplace because the accounting stock moved is one of the most expensive small mistakes a multichannel seller makes.

Template

Trendyol Commission Invoice Reconciliation

Every month, Trendyol's commission invoices are matched against the purchase bills recorded in Parasut. Commission invoices that were never entered are surfaced for accounting approval, and the approved ones are written back to Parasut as purchase bills. Marketplace sellers routinely miss these: unrecorded commission overstates profit and loses the VAT deduction.

📖 Blog: Paraşüt in the Zervanor Engine: e-Fatura, e-Arşiv and Reminders →

Frequently asked questions

What can I automate with Paraşüt?

34 actions are available — for example: Get Me, List Contacts, Get Contact, Create Contact, Update Contact, and more.

Which Paraşüt events can start a workflow?

2 triggers — for example: Sales Invoice Created, New sales invoice.

Can Paraşüt be used as an AI agent tool?

Yes. Every Paraşüt action automatically becomes a tool an AI agent can call — the same pack powers both your workflows and your agents.

How is the Paraşüt integration modelled?

Paraşüt is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.