Short answer: Drop the "HubSpot → List Contacts" 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 |
|---|---|---|---|
Limit limit | string | Optional | Limit. e.g. "10" |
Properties properties | string | Optional | Properties. Example: email,firstname,lastname,company |
After (cursor) after | string | Optional | Pagination cursor from previous response |
{"limit": "10","properties": "e.g. email,firstname,lastname,company","after": "e.g. eyJ..."}
{"paging": {"next": {"after": "eyJ..."}},"results": [{"id": "501","properties": {"email": "user@example.com","firstname": "John"}}]}
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.