Create Folk Note: 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
Person ID person_id	string	Required	—
Note Body content	string	Required	—

Sample request

{
  "person_id": "{{trigger.person_id}}",
  "content": "{{trigger.content}}"
}

Returns

{
  "id": "note_abc",
  "content": "...",
  "createdAt": "2026-05-11T00:00:00Z"
}

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

FAQ

Questions about Create Folk Note.

What does the Create Folk Note action do in Folk?

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.

What inputs does Create Folk Note require?

Required: Person ID, Note Body. 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 Create Folk Note support batch operations?

Yes. Run Create Folk Note 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