Create Document from ClickUp
curl --request POST \
--url https://api.docsautomator.co/createDocument \
--header 'Content-Type: application/json' \
--data '
{
"docId": "<string>",
"taskId": "<string>",
"async": true,
"webhookParams": {},
"skipEsign": true,
"actingUserEmail": "<string>",
"docTemplateLink": "<string>"
}
'Documents
Create Document from ClickUp
Trigger document generation for a ClickUp task via the API
POST
/
createDocument
Create Document from ClickUp
curl --request POST \
--url https://api.docsautomator.co/createDocument \
--header 'Content-Type: application/json' \
--data '
{
"docId": "<string>",
"taskId": "<string>",
"async": true,
"webhookParams": {},
"skipEsign": true,
"actingUserEmail": "<string>",
"docTemplateLink": "<string>"
}
'When your automation’s data source is set to ClickUp, you only need to pass the task ID. All field mapping, line items, and output settings are pulled from the DocsAutomator app automatically.
Additional fields like
For setup instructions on connecting ClickUp to DocsAutomator, see the ClickUp integration guide.
Endpoint
POST https://api.docsautomator.co/createDocument
Request Body
The automation ID. Find it on the automation’s settings page or via
GET /automations.The ClickUp task ID. DocsAutomator fetches all mapped fields from this task automatically.
When
true, returns immediately with a jobId (HTTP 202). Poll GET /job/{jobId} for the result.Custom parameters passed through to webhook notifications as
webhookParams (plus an identical additionalParams copy kept only for legacy integrations). The triggering taskId is folded in automatically; your own keys are never overwritten.When
true, skips e-signing for this request even if the automation has e-signing enabled. The document is generated and delivered normally (Drive save, email, webhook), but no signing session is started and no signing invitations are sent. Useful for two-step approval flows: generate a draft for review first, then re-run without skipEsign to send the document for signing. Also accepted as a query parameter (?skipEsign=true) on GET requests.Email address of the team member generating this document. When the automation’s email delivery (or e-signature email settings) has Send from the team member who generates the document enabled, the email is sent from this member’s own connected Gmail or Outlook account instead of the configured sender. The address must match a mailbox connected to the workspace; otherwise DocsAutomator falls back to the automation’s configured sender. Also accepted as a query parameter (
?actingUserEmail=...) on GET requests or as an X-Acting-User-Email request header (the header takes precedence). The in-app Generate button passes this automatically.Override the automation’s Google Doc template URL for this request only.
Example
curl -X POST https://api.docsautomator.co/createDocument \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"docId": "YOUR_AUTOMATION_ID",
"taskId": "YOUR_CLICKUP_TASK_ID"
}'
Response
{
"message": "success",
"pdfUrl": "https://files.docsautomator.co/..."
}
googleDocUrl, savePdfGoogleDriveUrl, and e-signature fields are included depending on your automation’s configuration. See the API data source page for the full list.Last modified on June 12, 2026
⌘I