Docs support tickets
in your Zaps

A support ticket starts with an email, a message left on the docs site or page feedback. After Revdoku saves a new message of a ticket, it posts a short event to the webhook URL of the bucket. A Catch Hook trigger in Zapier gives you that URL, and the Zap starts on each event.

Catch Hook is part of Webhooks by Zapier. Zapier includes it on its Professional, Team and Enterprise plans. In the API, a bucket holds the files of one docs site, the site and its support tickets. The event carries IDs only, so a later step reads the message.

1. Create a Zap. For the trigger, choose Webhooks by Zapier and the event Catch Hook.
2. In Pick Off A Child Key, enter data. The trigger then gives account_id, bucket_id, ticket_id, message_id and channel as separate fields.
3. Copy the webhook URL from the Test tab.
4. Create a Revdoku API key with Connect via API. Setting a webhook needs admin access to the bucket, which this key gets by default.
5. Get the ID of your bucket from GET https://api.revdoku.com/v1/buckets. It starts with bkt_.
6. Register the Zapier URL. Replace BUCKET_ID and YOUR_ZAPIER_WEBHOOK_URL in this command:

   curl -X PUT https://api.revdoku.com/v1/buckets/BUCKET_ID/webhook \
     -H "Authorization: Bearer $REVDOKU_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"webhook_url": "YOUR_ZAPIER_WEBHOOK_URL"}'

7. Send an email to the support address of the docs, or leave a message on the docs site. Then select Test trigger in Zapier.

If you do not use a terminal, ask an AI chat with the Revdoku connector to set the webhook.

API by Zapier is a premium app in beta, for requests with saved credentials. It needs a paid Zapier plan. It keeps your Revdoku key in a connection, not in the Zap step.

1. On the Zapier Apps page, select + Add connection. Choose API by Zapier.
2. Choose Static Headers (API key). In Headers, enter Authorization: Bearer YOUR_REVDOKU_KEY.
3. In Domain filter, enter api.revdoku.com. Zapier then sends this key to no other host.
4. In the Zap, add an API Request action with this connection. Send a GET request to this URL: https://api.revdoku.com/v1/buckets/{bucket_id}/tickets/{ticket_id}/messages/{message_id}

Map bucket_id, ticket_id and message_id from the trigger into the URL. The answer has data.message with the subject, the from_addresses, the body_text and an attachments list.

1. Webhooks by Zapier: Catch Hook
   Pick Off A Child Key: data
2. API by Zapier: API Request, GET
   https://api.revdoku.com/v1/buckets/{bucket_id}/tickets/{ticket_id}/messages/{message_id}
3. Slack: Send Channel Message
   Message Text: New support message ({channel}): {subject}
   https://app.revdoku.com/buckets/view?account_id={account_id}&id={bucket_id}&view=mailbox&email_id={message_id}

The link opens the ticket in the Revdoku dashboard, only for signed-in members of your account. There, the built-in support agent can write a draft reply from your docs. A person reads the draft and sends it.

To open an issue instead, replace step 3 with an action of your tracker, for example GitHub: Create Issue. Put the subject and the link in the issue, and keep the message text in Revdoku.

Each push to the connected GitHub branch publishes the docs site. To publish on a schedule instead, turn off Auto-publish GitHub updates on the Settings page of the site. Then a Zap publishes with the Revdoku API.

1. Schedule by Zapier: Every Week
2. API by Zapier: API Request, POST
   https://api.revdoku.com/v1/buckets/BUCKET_ID/publication
3. Delay by Zapier: Delay For, 5 minutes
4. API by Zapier: API Request, GET
   https://api.revdoku.com/v1/buckets/BUCKET_ID/publication
5. Slack: Send Channel Message
   Message Text: Docs site {publish_state}: {url} {publish_error}

The API by Zapier connection of this Zap needs a key with admin access to the bucket, for example the Connect via API key. A publish builds in the background. Step 4 reads its state: ready, failed, or still queued or processing.

For a 24-hour preview, use /publication/preview in steps 2 and 4. The preview has its own address, and the live site does not change. With auto-publish off, a push to another branch gets no preview.

If step 2 gives an unknown result, read the site before you publish again. The Publications API reference lists all fields.

Zapier also has an MCP Client app in beta. MCP is a standard way for AI apps to use outside tools, and each public docs site has an MCP server at /mcp. In the connection, set Server URL to https://docs.example.com/mcp, Transport to Streamable HTTP and OAuth to No. A Run Tool action can then call search_docs to find the docs page for a question.

For your Revdoku account, set Server URL to https://mcp.revdoku.com and OAuth to Yes. Then sign in to Revdoku. A Run Tool action can call a tool such as bucket_ticket_get.

• Keep the Catch Hook URL private. A fake event cannot bring message text into the Zap, because the Zap reads each message from Revdoku with your key.
• Give the API by Zapier connection that reads tickets its own key, with read access to this one bucket. You manage keys in Account → Access. Use an admin key only in a Zap that publishes.
• Do not paste the Revdoku key into a Code by Zapier step. Zapier states that Code by Zapier does not support secrets in code.
• The AI filter of Revdoku checks each new message first. The event waits until the check ends, at most about one minute. A message that the filter labels Junk sends no event.
• When a delivery fails, Revdoku sends the same event again. One message can then start two Zap runs and post two Slack messages. The event id is the same each time.
• When you no longer need the Zap, turn it off. Then send DELETE https://api.revdoku.com/v1/buckets/BUCKET_ID/webhook with the admin key, so Revdoku stops the events.

Zapier webhooks help · API by Zapier help · Zapier MCP Client help · Revdoku ticket events · Revdoku API guide