Update Category: 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
Category ID category_id	string	Required	Category ID
Name name	string	Optional	Name
Slug slug	string	Optional	Slug
Description description	string	Optional	Description

Sample request

{
  "category_id": "{{trigger.category_id}}",
  "name": "{{trigger.name}}",
  "slug": "{{trigger.slug}}",
  "description": "{{trigger.description}}"
}

Returns

{
  "id": "cat1",
  "name": "Tech",
  "slug": "tech"
}

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

FAQ

Questions about Update Category.

What does the Update Category action do in Typeflo?

Updates an existing Typeflo category's name, slug, or description. Only the fields you pass are changed.

What inputs does Update Category require?

Required: Category 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 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 Update Category support batch operations?

Yes. Run Update Category 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