Short answer: Drop the "HubSpot → Create Task" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Task Subject subject | string | Required | Task Subject. Example: Follow up with client |
Task Notes body | string | Optional | Message body content. Plain text unless the API specifies HTML/markdown. |
Task Type hs_task_type | options | Optional | Task Type. Options: To Do, Call, Email |
Due Date (epoch ms) hs_timestamp | string | Required | Timestamp in milliseconds since epoch. HubSpot rejects tasks without this. Pass Date.now() for 'now' or compute the desired due date in ms. |
Owner ID hubspot_owner_id | string | Optional | Owner ID |
{"subject": "e.g. Follow up with client","body": "e.g. Hi there, thanks for reaching out.","hs_task_type": "{{trigger.hs_task_type}}","hs_timestamp": "1712835600000","hubspot_owner_id": "{{trigger.hubspot_owner_id}}"}
{"id": "task123","properties": {"hs_task_type": "CALL","hs_task_subject": "Follow up with client"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.