Automation that runs on the server, not in a browser tab
Build flows on a visual canvas: pick the object and the event, set conditions with formulas, add actions on the met and not-met branches, and schedule follow-ups relative to any date. Every flow also fires for records that arrive through the API, web forms or webhooks, and every run leaves a trace.
Three kinds of flows
Runs when a record is created or updated. The met branch fires once, when the conditions become true; the not-met branch catches records that fall out.
Scans an object every day at the hour you choose, on the server. Each matching record is handled once, with a preview of how many records match before you save.
A step-by-step form your team runs from Quick Create, ending in a new record with the fields you chose.
Twelve actions, no code
Chain as many as you need on either branch. Values accept placeholders like {kayΔ±t} and {sahip}, any field of the record, or a formula.
Set a field on the triggering record with a value, a placeholder or a formula.
Change the parent this record points to: the case's account, the appointment's patient, the task's related record.
Update every linked child at once: an account's contacts, a patient's appointments.
Create a record in another object and link it back through a lookup field.
A task for the owner, linked to the record, with type and due date.
Hand the record to a user or a queue.
A bell notification for everyone or for the record owner.
Reach phones and browsers, even when the app is closed.
Templated or free-text email to the record's address.
A post on the record's timeline.
Email the survey, or open a send task when there is no address.
Send the record to an external system with a signed POST.
Conditions that think
amount * 1.2, IF(status = "New", 1, 0), TODAY(): arithmetic, text and date functions with a live preview while you type.
Fire only when a field actually changes, or changes to a specific value, exactly like ISCHANGED in Salesforce.
Up to ten conditions combined with all, any, or an expression like 1 AND (2 OR 3).
Actions that run a set time after the trigger or relative to a date field. Conditions are re-checked before they run.
Update the parent record, update every child record, or create a linked record in another object.
Core objects, industry objects like appointments and reservations, and your own custom objects and custom fields.
Built for the people who run it
Every run is logged: which flow, which record, which actions, from the app, the API, a web form, the scheduler or a scheduled path.
Ready-made flows per object under the canvas: critical case to urgent task, reminder before close date, overdue invoices to collection task, and more. One click loads them.
Every action explained in place: what it does and where it runs, so nobody needs the manual.
See how many records a scheduled flow will match before saving, and run it on demand.
Flows run even when nobody has the app open. API, Web-to-Lead, Web-to-Case, portal and store webhook writes trigger them too.
Scheduled flows remember what they already handled, so an overdue invoice gets one task, not one every morning.
Also in the box
Questions about automation
Do flows run when data comes in through the API or a web form?
Yes. The flow engine runs on the server, so records created by the REST API, Web-to-Lead, Web-to-Case, the partner portal or the store webhook trigger the same flows as records created in the app.
What is a scheduled path?
An action that runs a set time after the trigger or relative to a date field: a reminder three days before the close date, a follow-up seven days after a lead is created. Conditions are re-checked at run time, so a record that no longer qualifies is skipped.
Can a flow use formulas?
Every value can be a formula: field keys, arithmetic, text joins and comparisons, plus IF, AND, OR, NOT, ISBLANK, TODAY, DAYS, ROUND, ABS, MIN and MAX. A live preview shows the result while you type.
Will a scheduled flow spam the same record every day?
No. Scheduled flows remember which records they already handled and fire once per record. A record that stops matching and later matches again is picked up again.
Is there any code involved?
None. Flows are built on a visual canvas with a decision node, a met and a not-met branch, scheduled paths and a library of ready-made templates and an action guide underneath.
Automate your first process today
Load a template, adjust a condition, save. Included in every plan, no add-on.