Short answer: Drop the "Typeflo → Update Post" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Post ID post_id | string | Required | The Post ID assigned by Typeflo. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Title title | string | Optional | Title |
Content content | html | Optional | Content |
Slug slug | string | Optional | Slug |
Category category | dynamic-options | Optional | Category. (select from available options) |
Tags tags | string | Optional | Tags. e.g. "Comma-separated" |
Status status | options | Optional | Status. Options: Draft, Published, Scheduled |
SEO Title meta_title | string | Optional | SEO Title |
SEO Description meta_description | string | Optional | SEO Description |
Featured Image URL featured_image | string | Optional | Featured Image URL |
{"post_id": "{{trigger.post_id}}","title": "{{trigger.title}}","content": "{{trigger.content}}","slug": "{{trigger.slug}}","category": "{{trigger.category}}"}
{"id": "abc123","title": "Updated Title","status": "published"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.