The AI Generate step sends data to an AI model and returns text, structured data, email content, or a generated image. It supports four actions, each built for a different output type.

The Research Agent step searches the web and synthesizes findings using AI. It supports two actions: Search produces a narrative summary with citations, and Structured Search populates user-defined fields from the research results.

The Web Scrape step fetches a single URL and extracts the page content along with metadata like title, description, author, and published date.

The RSS Feed step fetches items from an RSS or Atom feed URL and parses them into a structured list for processing.

Format Email turns a header, body and footer into one complete email. It holds your branding (logo header, sign-off footer, an optional bordered card) in one place, lets you review and edit the finished email before it goes out, and supports per-recipient personalization. A Send Email step then delivers the result to each recipient.

The Send Email step sends an email with a subject line, body, and optional file attachments. You can also add a Header and Footer that wrap every send with consistent branding, like a logo at the top and a social links bar at the bottom. The body, header, and footer are rich text: format text, insert images, or switch to HTML mode when you want to paste in your own markup. It supports two sending modes: Formt for simple notifications, and Custom Domain for sending from your own verified domain.

The Gmail step sends email from the Gmail inbox your team has connected. Because it sends as your real address, the message lands in your own Sent folder and reads as a genuine one-to-one email rather than a bulk send. Any replies come straight back to that same inbox, so you automate the outreach but still receive and manage the responses personally, just as if you had written the email by hand. It can carry file attachments from earlier steps. Requires a connected Gmail account, which is separate from a Google Drive connection.

The Outlook step works with the Microsoft 365 mailbox your team has connected. It can send email from your real address so the message lands in your own Sent folder and reads as a genuine one-to-one email, stage a draft in your Drafts folder for a person to review and send by hand, or read recent messages from a mailbox folder so a workflow can react to what has arrived. Sends and drafts can carry file attachments from earlier steps. It needs a connected Outlook account, set up once from the integrations settings page.

The Email Tracking step queries the delivery service for engagement data about a previously sent email and automatically suppresses problematic addresses.

The Email Address Validation step checks whether an email address looks real and deliverable before you send to it. It is a best-effort check that catches clearly bad addresses and flags risky ones, which lowers your bounce rate and protects your sending reputation. A passing address is a strong signal, not a guarantee of delivery.

The Suppression List step unsubscribes an email address so they no longer receive workflow emails from your organization. Once unsubscribed, the Send Email step will automatically skip that address in future workflow runs. Use this step to programmatically manage your unsubscribe list as part of a workflow.

The Form step presents a form and turns the answers into data the rest of your workflow can use. Its main job is collecting information from people: intake details, requests, submissions, or a quick review and correction of data already in the run. A form can be private, viewable only inside Formt for your own team to fill in, or public: a form that people outside your team can open and submit without a Formt account. A public form at the start of a workflow gives you one shareable link and an embed snippet, and every submission starts a new run. A public form later in a workflow works the other way round: it gives you a link that is unique to each run, so you can send it to a specific person and their submission feeds back into the run it came from and continues it, rather than starting a new one.

The CSV step handles importing data from CSV files and exporting workflow data back out as CSV. It supports two actions: Import and Export.

A dataset is your own table of data that lives in Formt, so a workflow can remember things between runs instead of starting fresh each time. Use one to build up a list your workflows read and write over time (contacts, orders, a price book), to look up reference data mid-run, or to keep the same record from being processed twice. The Dataset step is how a workflow reads and writes those rows.

The PDF step handles all PDF operations in your workflow. It supports five actions: Extract, Extract Structured, Merge, Form Fill, and Create PDF.

The Google Sheets step connects your workflow to Google Spreadsheets. It supports five actions for reading, writing, and updating data. Requires a connected Google integration.

The Excel step reads and writes .xlsx workbooks. Several steps can build up one workbook across a single run: the first write creates the file, and later steps add tabs to it or append more rows to a tab it already has. No account needs connecting, and the finished workbook is a file you can download.

The QR Code step generates a QR code image from a URL input. The generated image is uploaded to storage and can be mapped to PDF or email steps for embedding or attachment.

The File Ingest step downloads a file, image, or PDF from a direct URL and stores it as an upload your workflow can reuse. The stored file can be attached to a Send Email step, posted to social, or embedded in a generated PDF.

The Property Lookup step takes a street address broken into components (street, city, state, and optional zip code) and returns detailed property information including bedrooms, bathrooms, square footage, year built, owner details, and property features. All input and output fields are pre-configured.

The Financial Data step fetches comprehensive financial information for a publicly traded company by ticker symbol. It returns current pricing, market cap, trading data, and historical financials covering revenue, income, cash flow, debt, and more. All fields are pre-configured.

The SEC Filing step fetches standardized financial data from SEC XBRL filings for a publicly traded company. It returns structured arrays sourced directly from regulatory filings, including revenue, net income, assets, liabilities, equity, and cash flow data across multiple fiscal years.

The Evaluate step evaluates mathematical expressions against input data and writes computed results to output fields. Expressions support arithmetic, comparisons, and built-in functions including array aggregations (mean, sum, min, max, stddev, first, last, firstNonZero, lastNonZero) and scalar math (abs, sqrt, ln, pow, round, cagr). Both input and output field sets are fully customizable.

The For Each step takes a list from a previous step and processes each item individually in parallel. It's the entry point of a loop that always ends with a Collect step.

The Collect step closes a For Each loop by waiting for all iterations to complete, then aggregating results into a single list with an item count and fail count. The output format matches import steps, making it directly compatible with CSV Export and Google Sheets Export steps.

The Filter step removes elements from an array based on conditions you define, outputting only the matching items. It has two actions: Filter, which keeps rows that match a condition, and Deduplicate, which collapses duplicate rows.

Deduplicate is one of the two actions on the Filter step. It collapses duplicate rows in a list down to one row per item, using the fields you choose as the identity key. Run it before a For Each loop or an export so you do not process or write the same record twice.

The Condition step is a decision node that routes execution down different paths based on conditions you define. Branches are evaluated top-to-bottom and the first matching branch runs while the others are skipped. An optional else branch catches anything that doesn't match.

The Schedule Run step books another one of your workflows to run one time at a future date and time, then finishes immediately so the rest of the current workflow keeps going. Reach for it when the follow-up should happen later, on its own schedule, rather than right now.

The Facebook step publishes posts to a connected Facebook Page. Requires a connected Facebook integration.

The Instagram step publishes an image, or a carousel of images, to your connected Instagram Business account with an optional caption. Requires a connected Instagram integration.

The LinkedIn step publishes posts to a connected LinkedIn profile or organization page. Requires a connected LinkedIn integration.

The Slack step sends messages to a connected Slack channel. Requires a connected Slack integration.

The WordPress step connects a workflow to your WordPress site. You can publish posts and events, correct an event that is already published, or pull existing posts and events back into the workflow for analysis and repurposing. Five actions cover both directions. Requires a connected WordPress integration.

The Calendly Booking trigger starts a new run whenever an invitee books or cancels a meeting on your connected Calendly account. It is a starting step: place it at the top of the workflow, and the booking details flow into the steps that follow. Requires a connected Calendly account.

The HubSpot step connects your workflow to a HubSpot portal so it can read contacts and companies, write them back, and log activity. Six actions cover the full CRM loop. Requires a connected HubSpot integration.

The AccuLynx step reads job data from your AccuLynx account so a workflow can act on it. You can look up a single job, list jobs by milestone and date, and read a job's contacts, estimate, and financial summary. Requires a connected AccuLynx integration.

The Xero step reads data from a connected Xero organisation so a workflow can analyze or reconcile it. You can pull invoices, bills, bank transactions, contacts, the chart of accounts, and named financial reports. Requires a connected Xero integration.

The AcquireUp step reads your seminars and the people who registered for them from a connected AcquireUp account, so a workflow can act on them automatically. List your seminars, then pull the registrants for any one of them. Requires a connected AcquireUp integration.

The WooCommerce step reads orders and products from a connected WooCommerce shop, so a workflow can act on every sale without anyone re-typing it. List the orders placed in a date range, filtered by status or product category, or list your products. The connection is read-only: it never changes an order or a product. Requires a connected WooCommerce integration.

The DonorPerfect step reads from a connected DonorPerfect database, so a workflow can check who someone is, which codes you use, what they have given, and whose membership is about to lapse, without anyone looking it up by hand. Find a constituent by donor ID, by email, or by name and ZIP code, list the codes for a field such as membership type, list gifts, or list the memberships expiring soon. The step only reads: it never adds or changes a record. Requires a connected DonorPerfect integration.