DocTransform

Zapier, Make and n8n

Send every finished Run to Zapier, Make or n8n with one address, no code needed

You do not need to write code. Zapier, Make and n8n can each give you a web address that waits for a message. Paste that address into DocTransform once, and every finished Run sends a message to your Zap, scenario or workflow, with a link to the file.

New to the idea? Webhooks explains it with a doorbell.

The recipe in four steps

  1. Get an address from your tool

    Create a Zap, scenario or workflow that starts with a catch-hook step, and copy the address it shows. The next section says where to click in each tool.

    This is what an address looks like (yours has other letters and numbers):

    https://hooks.example.com/catch/YOUR-ADDRESS
  2. Paste it into DocTransform

    Open your Account page, find the card called Webhooks and click Add Webhook. Paste the address into Address to send events to, then click Save Webhook.

  3. Send a test event

    Click Send test event. Your tool receives a sample message, and now it knows what the fields look like, so you can pick them in the next steps.

  4. Run a Template

    From now on every finished Run sends a message. Use the file link in it to email, save or pass on the file.

    A Run starts with an API Key: from a script, or from an HTTP step in your tool. See Your first API run. Downloading in the app does not send a Webhook.

Where to click in each tool

These are the names the tools showed when we checked, on 8 November 2026.

ToolGet the addressUse the file link
ZapierStart a Zap. For the trigger, choose the app Webhooks by Zapier and the event Catch Hook, then click Continue. Copy the address on the Test tab. After DocTransform has sent the test event, click Test trigger. Turn the Zap on, or it will not run.Pass the link to the next step, for example an email or a storage app.
MakeAdd the Webhooks app and choose the module Custom webhook. Click Add, give it a name and click Save. Copy the address it shows, and run the scenario once before you click Send test event. Switch the scenario on when it works.Add the HTTP app's Download a file module with the link as its URL, then send the file where you want it.
n8nAdd a Webhook node and set HTTP Method to POST. While you build, click Listen for test event and use the Test URL. When you are done, switch the workflow to active and use the Production URL instead.Add an HTTP Request node with the link as its address. Under Add Option choose Response and set Response Format to File.
Warning Treat the address your tool gave you like a password. Anyone who has it can send fake messages to your Zap, scenario or workflow, and the file link works for anyone until it expires. Never post either in a shared place.

What the message holds

The fields you will use most:

  • type: run.succeeded or run.failed. Stop the flow on anything else, because Send test event sends webhook.test.
  • data.download_url: the file link. It is empty when the Run failed.
  • data.expires_at: when the link stops working.
  • data.error.code: why a Run failed.

The full message, with an example of each type, is in What arrives.

If nothing arrives

Open the Webhook on your Account page and read its Delivery log: it says what your tool answered. The usual causes are a Zap that is off, a workflow that is not active while the Test URL is pasted, or an address copied with a missing character. A deleted Zap turns the Webhook off by itself. Every reason is explained in When deliveries fail.