Short answer: You can get post in Typeflo by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Typeflo Get Post action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
{"post_id": "e.g. abc123 or my-first-post"}
{"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.
Any of these apps can fire this action as part of a workflow.