AIDA Zapier

Zapier is a Destination (beta) that sends every document approved in AIDA to a Zap, so you can forward its data and PDF to thousands of apps (Google Sheets, Slack, your ERP and more).

Connect AIDA to Zapier

1. In AIDA, open the document type, add the Zapier destination and save.
2. Copy the destination's key.
3. In Zapier, create a Zap with the trigger AIDA → Document Approved. When asked to connect, paste the key. The connection is labeled with the document type name.
4. Test the trigger: Zapier loads the three most recent processed documents of that type as samples. Approve at least one document first.
5. Add the actions you need, map the fields and publish the Zap.

From now on, every document approved with this destination is sent to the Zap. The Open your Zaps button in the destination opens your Zaps in Zapier.

note

Each Zapier destination feeds one Zap: connecting a new Zap with the same key replaces the previous one. To feed several Zaps, add several Zapier destinations. Regenerating the key disconnects the Zap.

If the Zap is turned off or deleted, the destination is disconnected and new approvals end with the error zapierNotConnected until a Zap is connected again.

---

Payload

Each approved document is sent as a JSON object. The sample records shown in Zapier have the same format.

Field	Type	Description
id	string	The AIDA document ID.
documentName	string	The document name.
documentConfigurationName	string	The document type name.
documentURL	string	A permanent link to view the document within the AIDA web application.
downloadURL	string	A temporary, secure link to download the document's PDF file. It expires after 7 days.

The extracted properties follow the same rules as the Webhook destination: the key is the property's Output Mapping or, if not set, its Label, values are cast to their JSON type and tables become arrays. Unlike the webhook, dates are ISO-8601 UTC strings (for example 2025-10-14T00:00:00Z).

{
  "Invoice number": "INV-2025-042",
  "invoiceDate": "2025-10-14T00:00:00Z",
  "total": 122.00,
  "lines": [
    { "description": "Product A", "qty": 2, "unitPrice": 50.00 }
  ],
  "id": "12345",
  "documentName": "invoice-042.pdf",
  "documentConfigurationName": "Invoice",
  "documentURL": "https://www.aidacloud.com/app/web/archive/12345",
  "downloadURL": "https://api.aidacloud.com/asset/document/generated-auth-token"
}

---

API reference

The AIDA Zapier app uses the following endpoints. The base URL is https://api.aidacloud.com/api/v1/zapier.

Authentication: every request sends the destination key in the X-API-Key header. A missing or unknown key returns 401 Unauthorized.

Method	Path	Purpose	Body	Response
GET	/me	Tests the connection.	-	{ "id", "documentConfigurationId", "documentConfigurationName", "username" }
POST	/hooks	Subscribes the Zap (REST hook). The URL must start with https://hooks.zapier.com/, otherwise 400.	{ "hookUrl": "…" }	{ "id" }
DELETE	/hooks	Unsubscribes the Zap. It only disconnects the destination if hookUrl is the one currently connected.	{ "hookUrl": "…" }	empty
GET	/documents/sample	Returns up to three recent processed documents of the document type, in the payload format.	-	array of payloads

Delivery: when a document is approved, AIDA sends an HTTP POST with the payload to the subscribed hook, with Content-Type: application/json. If Zapier answers 410 Gone, AIDA disconnects the destination.