Short answer: Drop the "Affinity → List People" 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 term | string | Optional | Search. e.g. "Search by name or email" |
Page Size page_size | number | Optional | Page Size |
{"term": "Search by name or email","page_size": "{{trigger.page_size}}"}
{"persons": [{"id": 123,"emails": ["john@example.com"],"last_name": "Doe","first_name": "John","organization_ids": [456]}]}
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.