Documo integration

What it does

The Documo integration lets your agency drive a client's electronic fax program from inside a workflow. Connect a client's Documo account once and your workflows can send outbound faxes with cover pages and PDF attachments through the v1 REST API, page through outbound and inbound fax history, look up a single fax by id, list the fax numbers and contacts on the connected account, and react in real time when Documo posts a fax-completed or fax-received event to the configured webhook URL.

Connect a Documo account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Documo and click Connect.
3. In a new tab, open the Documo dashboard signed in as the client (or as your agency, if the client has delegated key creation to you).
4. Go to Settings, Developer, API Keys and create a new API key. Copy the API key id and API key secret.
5. Paste the API key id and API key secret into TaskJuice. Both values are sent as HTTP Basic credentials on every request.

To rotate or revoke the key, return to the Documo API keys page, generate a new pair, and update the TaskJuice connection.

Triggers

• documo/fax-completed fires when an outbound fax reaches a terminal status (success or failure) on the connected Documo account. One POST per event, with the fax id, terminal status, page count, transmission duration, and any tags carried on the original send.
• documo/fax-received fires when the connected Documo account receives an inbound fax. One POST per event, with the inbound fax id, caller id, page count, and a URL to the received fax PDF.

Each trigger publishes an inbound URL. Paste it into Documo under Settings, Developer, Webhooks, copy the webhook secret Documo generates, and paste that secret into the TaskJuice trigger. TaskJuice verifies the HMAC-SHA256 hex signature Documo sends on the X-Documo-Signature header before activating the workflow.

Actions

• documo/send-fax sends an outbound fax to one or more recipients through the v1 /faxes endpoint, with optional cover page, subject, notes, tags, and one or more PDF attachments by URL or base64 payload.
• documo/list-faxes pages through faxes on the connected account, optionally filtered by direction (inbound or outbound), status, date range, and tag.
• documo/get-fax retrieves a single fax by id, including its delivery status, page count, transmission duration, and recipient metadata.
• documo/list-numbers pages through the fax numbers owned by the connected Documo account.
• documo/list-contacts pages through the contacts (fax-address book entries) on the connected Documo account, with optional free-text search across name, organization, and fax number.

Known limitations

• The integration uses Documo's v1 REST API with the connected account's API key id and secret. Per-account rate limits, monthly page caps, and pricing are governed by the client's Documo plan, not by TaskJuice. When Documo returns a 429, the action surfaces as a retryable rate-limit error and honors the recommended backoff.
• Outbound caller id must be a fax number owned by the connected account. Documo returns a 422 if the caller id is not on the account, which surfaces as a validation error.
• Inbound webhook verification uses HMAC-SHA256 with hex encoding on the raw request body. Treat the webhook secret as sensitive and rotate it alongside the API key.
• Attachments can be supplied either as base64-encoded data or as publicly reachable URLs. Documo fetches URLs at send time, so the URL must remain reachable until the fax leaves the queue.
• The documo/get-fax action returns metadata only. To download the fax PDF, use the fileUrl field returned on the fax resource and fetch it with the same API credentials.