Short answer: Drop the "Apollo.io → Search 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 |
|---|---|---|---|
Job Titles person_titles | string | Optional | Comma-separated |
Company Domains q_organization_domains | string | Optional | Company Domains. e.g. "stripe.com, shopify.com" |
Locations person_locations | string | Optional | Locations. e.g. "San Francisco, New York" |
Results per Page per_page | number | Optional | Results per Page |
{"person_titles": "CEO, CTO, VP Engineering","q_organization_domains": "stripe.com, shopify.com","person_locations": "San Francisco, New York","per_page": "{{trigger.per_page}}"}
{"people": [{"id": "person123","email": "john@company.com","title": "CEO","last_name": "Doe","first_name": "John","linkedin_url": "https://linkedin.com/in/johndoe","organization": {"name": "Company Inc"}}],"pagination": {"total_entries": 500}}
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.