How to update folk person in Folk

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
Person ID person_id	string	Required	–
Full Name fullName	string	Optional	–
Job Title jobTitle	string	Optional	–
Description description	string	Optional	–

Sample request

{
  "person_id": "{{trigger.person_id}}",
  "fullName": "{{trigger.fullName}}",
  "jobTitle": "{{trigger.jobTitle}}",
  "description": "{{trigger.description}}"
}

Returns

{
  "id": "person_abc",
  "fullName": "Jane Doe"
}

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

FAQ

Questions about Update Folk Person.

What does the Update Folk Person action do in Folk?

Partial update — only passed fields change. For "Clearbit enriched this person → write back to Folk" augmentation workflows.

What inputs does Update Folk Person require?

Required: Person ID. 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 Update Folk Person support batch operations?

Yes. Run Update Folk Person inside a Loop node to process arrays. TinyCommand handles Folk's rate limits automatically so you don't have to throttle manually.

More actions