Create Note: Attio 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
Parent Object parent_object	options	Required	—
Parent Record ID parent_record_id	string	Required	—
Title title	string	Optional	Discovery call notes
Body content	string	Required	—
Format format	options	Optional	—

Sample request

{
  "parent_object": "{{trigger.parent_object}}",
  "parent_record_id": "{{trigger.parent_record_id}}",
  "title": "Discovery call notes",
  "content": "{{trigger.content}}",
  "format": "{{trigger.format}}"
}

Returns

{
  "data": {
    "id": {
      "note_id": "note_abc123"
    }
  }
}

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

FAQ

Questions about Create Note.

What does the Create Note action do in Attio?

Attaches a note to a person, company, or other Attio object. Notes appear in the record's activity timeline. Useful for "AI-summarised call notes → log to the contact" workflows that keep the CRM annotated automatically.

What inputs does Create Note require?

Required: Parent Object, Parent Record ID, 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 Attio 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 Note support batch operations?

Yes. Run Create Note inside a Loop node to process arrays. Tiny Command handles Attio's rate limits automatically so you don't have to throttle manually.

More actions