After a form comes in
An event request, already sorted.
A planner at Parc Léopold Events sends the request form on your site. The automation finds the contact, creates a deal in the right pipeline and sets Sofia as its owner.
Automations
Checking availabilityComing soonLet the workspace handle the repetitive steps.
When a record changes or a form comes in, an automation checks your conditions, updates records or calls a webhook. Every run is logged, step by step.
A visual builder for the steps you repeat
Pick a trigger, add conditions and actions, and read the whole flow from top to bottom. Automations find the right record, create or update what needs to change and send a webhook to your other systems. If a flow keeps failing, it pauses itself until someone takes a look.
Triggers, conditions and actions, in plain sight
An automation starts when a record is created or changed, a form is submitted or an installed app reports an event. IF conditions decide whether it goes on. Lookups find the record to act on before anything is changed.
Triggers from real events
A new record, a changed field, a form submission or an event from an installed app.
IF conditions
Check any field first, so a large deal and a small one don’t get the same treatment.
Find the right record
Look up a company, a contact or any other record before acting on it.
Create and update records
Create a record, or set a status and fill in fields on the one you just found.
Reach your other tools and see every run
Outgoing webhooks send record data to the systems you already use, with headers that let them ignore duplicates. Installed apps can add their own steps. Every run keeps a result per step, and a flow that keeps failing pauses itself.
Outgoing webhooks
Send record data to the URL you choose, with dedupe headers so your system can spot a retry.
Steps from installed apps
Apps you install can add their own actions, listed next to the built-in ones.
Run history, step by step
Open any run to see which steps passed, what they did and where one stopped.
Pauses itself when failing
After repeated failures an automation is paused, so a broken flow stops piling up errors.
The follow-through, without a reminder
Three moments in an ordinary week where an automation takes the next step and keeps a record of what it did.
When a deal is wonThe win reaches your other systems.
Tom moves Delcourt to Won. The automation marks the company as a client and sends the deal to your own systems through a webhook, with a header that lets them spot a retry.
Thursday, 16:00A failing flow, paused before it piles up.
A partner changed its URL and the webhook keeps failing, so the automation pauses itself. Jonas opens the run history, sees the step that stopped, fixes the address and turns it back on.
Workflows that follow the way your team works.
In a 30-minute demo, describe a step your team still does by hand and watch it become an automation in Squario.
Questions about automations
Which plans include automations?
Automations are included on paid plans. The Free plan doesn’t include them.
Can an automation call another tool?
Yes. Any automation can call an outgoing webhook, with deduplication headers so the receiving system can ignore repeats. Installed apps can also add their own steps.
What happens when an automation fails?
Each run is logged with a result per step, so you can see where it stopped. If an automation keeps failing, it is paused automatically.
Do I need to write code?
No. Triggers, conditions, lookups and actions are set up in a visual builder, without code.