Short answer: Drop the "Typeflo → Create Category" 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 |
|---|---|---|---|
Name name | string | Required | Name. Example: Engineering |
Slug slug | string | Optional | Slug. Example: engineering (auto-generated if empty) |
Description description | string | Optional | Description |
{"name": "e.g. Engineering","slug": "e.g. engineering (auto-generated if empty)","description": "{{trigger.description}}"}
{"id": "cat1","name": "Engineering","slug": "engineering"}
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.