Short answer: Drop the "Xero → 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 |
|---|---|---|---|
Filter where | string | Optional | Filter. e.g. "ContactStatus=="ACTIVE"" |
{"where": "ContactStatus==\"ACTIVE\""}
{"Contacts": [{"Name": "John Doe","ContactID": "abc123","EmailAddress": "john@example.com","ContactStatus": "ACTIVE"}]}
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.