Nilvera

Also an agent tool

finance-billing

Turkish GİB e-document integrator: e-Fatura & e-Arşiv invoice issuance and status tracking over a single Bearer API key; production + test (sandbox) environments.

Provider API docs ↗

9 actions · 5 triggers

The Nilvera integration lets you connect Nilvera to your automations with 9 actions and 5 triggers — and every action is also a tool an AI agent can call. Examples: Get Company, Check e-Fatura Taxpayer, Send e-Fatura (Model), Send e-Arşiv (Model), Get e-Fatura Status. 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 5

Events in Nilvera that can start a workflow.

webhook

Incoming Invoice Received

Fires when a new incoming e-Fatura arrives (polling list_incoming_einvoices).

webhook

Outgoing Invoice Status Changed

Fires when an outgoing e-Fatura status changes (polling list_outgoing_einvoices).

polling

When an outgoing invoice status changes

Polls issued e-Faturas in a moving date window; emits on new/changed status.

polling

When an incoming invoice arrives

Polls received e-Faturas in a moving date window; emits on each new incoming invoice.

polling

List e-Arşiv Invoices

List e-Arşiv invoices, paged and filtered by a date window and status.

Actions 9

What Zervanor can do in Nilvera.

Einvoice4

POST

Send e-Fatura (Model)

Issue + send an e-Fatura from a JSON invoice model. Returns a UUID. A 200 means 'accepted for processing', not GİB acceptance — poll get_einvoice_status until the status settles.

GET

Get e-Fatura Status

Get the government (GİB) processing status of a sent e-Fatura by UUID (unknown|waiting|succeed|error).

GET

List Outgoing e-Faturas

List issued (outgoing) e-Faturas, paged and filtered by a date window. Polling source for outgoing-status changes.

GET

List Incoming e-Faturas

List received (incoming) e-Faturas, paged and filtered by a date window. Polling source for newly arrived invoices.

Earchive3

POST

Send e-Arşiv (Model)

Issue + send an e-Arşiv invoice from a JSON invoice model (used when the buyer is not a registered e-Fatura taxpayer). Returns a UUID.

GET

List e-Arşiv Invoices

List e-Arşiv invoices, paged and filtered by a date window and status.

PUT

Cancel e-Arşiv Invoice

Cancel an issued e-Arşiv invoice by UUID. Cleanup action for the e-Arşiv write test target (reversible in sandbox).

General2

GET

Get Company

Read your own Nilvera company profile. Safe, idempotent connectivity/identity check.

GET

Check e-Fatura Taxpayer

Look up whether a tax number (VKN/TCKN) is a GİB-registered e-Fatura taxpayer. Drives the e-Fatura vs e-Arşiv routing decision.

Automations using Nilvera

Template

Rejected e-Invoice Patrol v2

Each morning the last seven days of outgoing e-Invoices are checked against the tax authority's status. Any that came back rejected or errored are collected and the accountant gets one SMS with the count and the total at risk. A clean week produces no message at all. Rejected e-Invoices are easy to miss because nothing in the accounting package changes when the rejection happens — the money is simply never collectable until someone notices.

Frequently asked questions

What can I automate with Nilvera?

9 actions are available — for example: Get Company, Check e-Fatura Taxpayer, Send e-Fatura (Model), Send e-Arşiv (Model), Get e-Fatura Status, and more.

Which Nilvera events can start a workflow?

5 triggers — for example: Incoming Invoice Received, Outgoing Invoice Status Changed, When an outgoing invoice status changes, When an incoming invoice arrives.

Can Nilvera be used as an AI agent tool?

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

How is the Nilvera integration modelled?

Nilvera 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.