Short answer: Drop the "Intercom → Search 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 |
|---|---|---|---|
Search Field field | options | Required | Search Field. Options: Email, Name, Phone, Role, External ID, Created At, Updated At |
Operator operator | options | Required | Operator. Options: Equals, Not Equals, Contains, Starts With, Greater Than, Less Than |
Search Value value | string | Required | Search Value. Example: user@example.com |
Per Page per_page | string | Optional | Results per page (max 150) |
{"field": "{{trigger.field}}","operator": "{{trigger.operator}}","value": "e.g. user@example.com","per_page": "50"}
{"data": [{"id": "63a07ddf05a32042dafac602","name": "John Doe","role": "user","type": "contact","email": "user@example.com","created_at": 1700000000}],"type": "list","pages": {"type": "pages","per_page": 50,"total_pages": 1},"total_count": 1}
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.