Overview
Utility actions are the small declarative steps that make automations boring in the best way. Reach for them when you need to format a date, pull a field out of JSON, run math, or match a regular expression without an extra Ask AI call.
TL;DR: Seven utility actions cover the everyday plumbing inside Taskade automations: Format Date, Extract JSON, Get Field, Text Replace, Regex Match, Calculate, and Lookup. They are fast, predictable, and cheaper than asking AI to do simple work. See the full Automation Actions reference.
The seven utilities
| Action | What it does |
|---|---|
| Format Date | Convert a date into a target format and timezone |
| Extract JSON | Run a JSONPath expression against any payload to pull a value |
| Get Field | Read one named field from a JSON object |
| Text Replace | Find-and-replace inside a string |
| Regex Match | Match a string against a regular expression and return groups |
| Calculate | Run math expressions over flow variables |
| Lookup | Pull a value from a table by key |
When to use a utility instead of AI
Utilities are deterministic, fast, and cheap. Reach for them when:
- The transform is well-defined (math, formatting, extraction)
- You need the same answer every run
- You want to keep credits low on the hot path
Reach for Ask AI when the transform needs reasoning, summarization, or pattern recognition.
Format Date
Format Date converts any date string or timestamp into the format your downstream step expects. Useful before posting to Slack, writing into a Taskade Project's Table view, or stamping a project title.
Extract JSON and Get Field
Both pull a value out of structured data. Use Get Field for a known top-level key. Use Extract JSON when the value is nested or you need a JSONPath expression like $.items[0].name.
Text Replace and Regex Match
Text Replace swaps a literal substring. Regex Match runs a regular expression and returns the matched groups, which you can then pipe into the next action.
Calculate and Lookup
Calculate evaluates math expressions including variables from prior steps. Lookup pulls a value from a small reference table by key, perfect for status maps and code-to-label translations.
Combine them
Most flows chain two or three utilities together. A common pattern: Webhook trigger โ Extract JSON โ Format Date โ Set Project Title.
Related guides
- Automation Actions. Full action reference.
- Ask AI Action. When you need reasoning.
- Webhooks. Pair with Extract JSON for incoming payloads.
- Filter Data. Conditional flow control.
- Branch Action. Multi-path workflows.