Short answer: Drop the "Folk → Create Folk Person" 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 |
|---|---|---|---|
Group ID group_id | string | Required | The Group ID assigned by Folk. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Full Name fullName | string | Required | — |
Emails (array of strings) emails | array | Optional | — |
Phone numbers (array of strings) phones | array | Optional | — |
Description description | string | Optional | — |
Job Title jobTitle | string | Optional | — |
Company Name companyName | string | Optional | — |
{"group_id": "{{trigger.group_id}}","fullName": "{{trigger.fullName}}","emails": "{{trigger.emails}}","phones": "{{trigger.phones}}","description": "{{trigger.description}}"}
{"id": "person_abc","emails": ["jane@acme.com"],"fullName": "Jane Doe","jobTitle": "CEO"}
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.