ActionFolkUpdated September 2026

How do I look up a Folk person by email?

Short answer: You can find folk person by email in Folk by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Folk Find Folk Person by Email action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Find Folk Person by Email in Folk — start free All 6 Folk actions

Find Folk Person by Email in Folk — start free

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.

Triggered by

Apps that pair well as the trigger for Find Folk Person by Email.

Any of these apps can fire this action as part of a workflow.

2 Google Sheets triggers

HubSpot → Folk

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Folk returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Find Folk Person by Email support batch operations?

Run Find Folk Person by Email inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Folk's rate limits.

More actions