Find Folk Person by Email: Folk action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Email email	string	Required	The email address. Used as the recipient or identifier depending on context.
Limit to Group ID (optional) group_id	string	Optional	The Limit to Group ID (optional) assigned by Folk. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.

Sample request

{
  "email": "e.g. user@example.com",
  "group_id": "{{trigger.group_id}}"
}

Returns

{
  "data": [
    {
      "id": "person_abc",
      "emails": [
        "jane@acme.com"
      ],
      "fullName": "Jane Doe"
    }
  ],
  "total": 1
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Find Folk Person by Email.

What does the Find Folk Person by Email action do in Folk?

Returns the first matching person by email. The standard "find before create" pattern; returns empty if no match for branching logic.

What inputs does Find Folk Person by Email require?

Required: Email. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Folk returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Find Folk Person by Email support batch operations?

Yes. Run Find Folk Person by Email inside a Loop node to process arrays. Tiny Command handles Folk's rate limits automatically so you don't have to throttle manually.

More actions