Skip to main content
The Notify Webhook feature allows DocsAutomator to send notifications to external services when documents are successfully generated. This enables integration with other applications and workflows.

​
Purpose

Notify other services about successful document creations through webhook callbacks, allowing you to trigger downstream processes or log document generation events in external systems.

​
Configuration

​
Webhook URL Registration

Register a webhook address that will receive notifications once documents are created. DocsAutomator makes POST requests to your specified endpoint when generation completes.
1

Open Output Settings

Navigate to your automation’s output configuration
2

Enable Webhook

Enable the “Notify Webhook” option
3

Enter URL

Enter your webhook endpoint URL
4

Test

Generate a preview document to test the webhook

​
Additional Parameters via API

The system supports sending supplementary data alongside webhook notifications through the webhookParams object in API requests. 
{
  "docId": "your-automation-id",
  "data": {
    "customer_name": "Acme Corp"
  },
  "webhookParams": {
    "orderId": "ORD-12345",
    "customerId": "CUST-789"
  }
}
These parameters appear in the webhook payload sent to your endpoint under two keys with identical content: webhookParams (matching the request parameter name) and additionalParams (the original key, kept for backward compatibility). Use whichever you prefer — existing integrations built on additionalParams keep working unchanged.

​
Webhook Payload Structure

{
  "pdfUrl": "https://...",
  "googleDocUrl": "https://docs.google.com/document/d/...",
  "documentName": "Invoice #123",
  "status": "completed",
  "webhookParams": {
    "orderId": "ORD-12345",
    "customerId": "CUST-789",
    "recId": "recAbC123XyZ"
  },
  "additionalParams": {
    "orderId": "ORD-12345",
    "customerId": "CUST-789",
    "recId": "recAbC123XyZ"
  }
}

​
Trigger Record Identifier

The identifier of the record that triggered the generation is included automatically, so you can match webhook notifications to records in your data source:
  • Airtable, SmartSuite, Notion: recId (Notion pageId and button triggers are normalized to recId)
  • ClickUp: taskId
  • Google Sheets: rowNumber — positional at trigger time, so treat it as “which row triggered this” rather than a durable key
Your own webhookParams keys are never overwritten by the automatic identifier.

​
Use Cases

CRM Updates

Update customer records when documents are generated

Workflow Triggers

Trigger downstream automation workflows

Logging

Log document generation events to external systems

Notifications

Send alerts to team collaboration tools
Last modified on June 12, 2026