Formatter
Formatter prepares data for later Workflow Steps without writing custom code. Use it to format dates, calculate numbers, clean text, extract values, or convert lists. It does not send the following Action's message or write its record.
Add and configure Formatter
- Select an add-step control and choose Formatter.
- In Setup, keep Formatter by FastHook as the app and select an Action event category.
- Select Continue. In Configure, choose a Transform.
- Complete its required inputs and options, then continue to Test.
- Select Test step, inspect Data in, Data out, and Warnings, and save the Step.
Changing category or transform can replace the input fields. Review the new inputs and retest instead of assuming the previous operation's settings still apply.
Choose an operation
| Category | Examples in the current catalog |
|---|---|
| Date / Time | Format, Add/Subtract Time, Compare Dates. |
| Numbers | Format Number, Format Currency, Perform Math Operation, Format Phone Number, Spreadsheet-Style Formula. |
| Text | Trim Whitespace, Split Text, Replace, Default Value, casing, extraction, URL encoding, and length. |
| Utilities | Import CSV, Lookup Table, Pick from List, Text to Line-item, Line-item to Text. |
The operation's description and fields define its supported behavior. A familiar spreadsheet name does not imply every spreadsheet function or formatting token is supported.
Bind the input
Use Value for a constant, Field for available Trigger or earlier Step data, or Template to combine text with inserted data where offered. Field opens the data picker; select the value rather than typing the sample as a constant.
Preset fields can offer Static / Custom. Static chooses a listed value; Custom permits the supported custom or mapped setting. Check the resulting format or timezone after changing modes.
For lists and JSON, preserve structured values rather than flattening them into display text. See Data mapping.
Example: clean a name
Choose Text → Trim Whitespace and map the name into Input. For an input consisting of spaces, Ada, and trailing spaces, the output is Ada. Test the value, then select this Step's output in the next Action.
Trimming the name does not change an Action that still maps the original Trigger field. Reopen that Action and choose the Formatter output explicitly.
Example: format Unix seconds
Choose Date / Time → Format, map the timestamp, and use From Format = X for Unix seconds. With input 1704067200, a UTC output timezone, and To Format = YYYY-MM-DD, the date is 2024-01-01.
Unix seconds and milliseconds are different inputs. Use an explicit input format and timezone rather than assuming the provider's timestamp convention. Invalid dates and daylight-saving gaps fail. Time-only input uses the event ingestion time as its date anchor so a retry does not substitute a new current date.
The supported formats use a bounded Moment-style token set. In this formatter, Z produces an offset without a colon and ZZ includes a colon. Use the preset controls and test the actual result before relying on a custom format.
Understand outputs and specialized operations
Formatter returns an object. Many operations put their scalar or list result under output. Some also return extra fields: Compare Dates includes normalized times and duration details; Import CSV can include headers and line items. Inspect Data out and choose the intended field downstream.
Import CSV accepts CSV content or a supported attachment from an earlier Step. Choose the file or content input, delimiter, and header behavior, then inspect the parsed rows. Do not assume that selecting one row preview processes the whole file; use a Loop for one Action per row.
Lookup Table uses case-sensitive keys and can provide a fallback. Pick from List uses zero-based custom indexes; negative indexes count from the end. Spreadsheet-Style Formula exposes Supported functions in its description; use those functions and inspect missing-value behavior.
Number parsing requires clean numeric input rather than currency symbols or grouping separators. Format Currency changes presentation, not exchange rates. Text length counts Unicode code points.
Test representative inputs and limits
Use Retest step after changing inputs, the operation, or an upstream sample. Test missing fields, empty lists, zero, negative numbers, and unexpected text where relevant. A successful sample does not guarantee every provider event has the same type or shape.
Resolved input and output are each limited to 1 MiB, strings to 262,144 code points, line-item operations to 10,000 items, and lookup tables to 1,000 rows. A subsequent Loop has its own lower item limit.
For structural JSON edits or custom reusable logic, see Workflow transformations. Use Run history to compare Formatter input, output, and the receiving Action's actual mapped input.