Get Post: Typeflo 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
Post ID or Slug post_id	string	Required	Post ID or Slug. Example: abc123 or my-first-post

Sample request

{
  "post_id": "e.g. abc123 or my-first-post"
}

Returns

{
  "id": "abc123",
  "slug": "my-first-post",
  "tags": [],
  "title": "My First Post",
  "author": {
    "name": "Jane"
  },
  "status": "published",
  "content": "<p>Hello world</p>",
  "categories": []
}

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

FAQ

Questions about Get Post.

What does the Get Post action do in Typeflo?

Fetches a single Typeflo blog post by ID or slug, returning the full body, metadata, and SEO fields. Use to mirror content into a CDN or to render previews.

What inputs does Get Post require?

Required: Post ID or Slug. 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 Typeflo 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 Get Post support batch operations?

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

More actions