How to update outline document in Outline

Update Outline Document in Outline — 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
Document ID id	string	Required	–
Title title	string	Optional	–
Markdown Body text	string	Optional	–
Append (instead of replace) append	options	Optional	–

Sample request

{
  "id": "{{trigger.id}}",
  "title": "{{trigger.title}}",
  "text": "{{trigger.text}}",
  "append": "{{trigger.append}}"
}

Returns

{
  "data": {
    "id": "doc_abc",
    "title": "Spec v2"
  }
}

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

FAQ

Questions about Update Outline Document.

What does the Update Outline Document action do in Outline?

Updates markdown content. Optional append=true mode adds to existing content with a separator (useful for daily-log docs).

What inputs does Update Outline Document require?

Required: Document 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 Outline 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 Outline Document support batch operations?

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

More actions