The processes nobody submits
A renewal that comes due. A row somebody edits. A system that posts to you. These start on their own, run without waiting for anyone, and stop when the work is done.
- Three ways to start without a form
- On a schedule, when a row changes in a table you name, or when a webhook arrives. A schedule can fan out one run per matching row, which is how a renewal watch marks everything ending inside 45 days.
- Write back onto the row
- An automation node can set columns on the record it is about, so the board and the decision are the same fact rather than two that drift apart.
- Wait, then carry on
- Park a run until a date or for a duration. It resumes on its own — no polling loop for anybody to maintain, and the run says plainly that it is waiting rather than looking stuck.
- Call other systems over HTTP
- Pull data in before a decision, or push it out after one. Credentials are configured once per API and encrypted at rest with AES-256-GCM; they are never returned by an API response.
- Tell people
- Email on assignment, on a status being reached, or from a step of your own — with the record's own values in the message.
Templates that use it
- AppCRMCompanies, the people in them, what you sell, the deals in play, plus the subscriptions, renewals and approvals that come after you win.
- FormCategorize FeedbackAI files each piece of feedback as a bug, a feature request, a question or praise, and hands it to a person when it is not sure. The submitter sees one "Completed" status either way.
What it does not do
- There is no one-click integration directory. Each connector is set up once against that system's own API.
- No database connector, so an automation cannot read or write an external Postgres, MySQL or Sheets directly.