Start free
ActionFolkUpdated June 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.

FieldTypeRequiredDescription
Email
email
stringRequiredThe email address. Used as the recipient or identifier depending on context.
Limit to Group ID (optional)
group_id
stringOptionalThe 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.

Gmail → Folk
1 Gmail triggers
Slack → Folk
13 Slack triggers
Google Sheets → Folk
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 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. TinyCommand handles Folk's rate limits automatically so you don't have to throttle manually.
More actions

Other Folk actions.

Action
Create Folk Company
Creates a company record in Folk CRM with name, domain, custom fields. Useful for "new B2B prospect → add company record before contact" workflow patterns.
Action
Create Folk Note
Attaches a markdown note to a person or company in Folk. For "call summary → log in CRM" or "customer feedback → add to their record" workflows.
Action
Create Folk Person
Creates a person record with email, name, company association, custom fields. The base hook for "form submission → push to Folk" sync workflows in relationship-driven agencies and consultancies.
Action
List Folk Groups
Returns every group (Folk's list/segment construct) with name and member count. Useful for resolving group IDs at workflow setup.
Action
Update Folk Person
Partial update — only passed fields change. For "Clearbit enriched this person → write back to Folk" augmentation workflows.
Find Folk Person by Email in Folk — start free