Create Outline Document: Outline 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
Title title	string	Required	—
Markdown Body text	string	Required	—
Collection ID collectionId	string	Required	—
Parent Document ID parentDocumentId	string	Optional	—
Publish? publish	options	Optional	—

Sample request

{
  "title": "{{trigger.title}}",
  "text": "{{trigger.text}}",
  "collectionId": "{{trigger.collectionId}}",
  "parentDocumentId": "{{trigger.parentDocumentId}}",
  "publish": "{{trigger.publish}}"
}

Returns

{
  "data": {
    "id": "doc_abc",
    "url": "/doc/spec-abc",
    "title": "Spec",
    "urlId": "spec-abc"
  }
}

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

FAQ

Questions about Create Outline Document.

What does the Create Outline Document action do in Outline?

Creates a new markdown document in a specific collection. Optional parent document for hierarchy. For "auto-publish meeting notes to wiki" or "doc-as-code from Git" workflows.

What inputs does Create Outline Document require?

Required: Title, Markdown Body, Collection 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 Create Outline Document support batch operations?

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

More actions