Build it by describing it
Describe the routine in your own words and Synapse builds the steps, checks them and schedules it. No flow to draw.
Synapse Operations
What your team redoes every Mondayruns on its own and stops where someone decides.
You draw the routine once. From then on it runs on a schedule or when something happens on the platform, and at the point where the business rule needs a person the run stops and waits for the decision.
- The approval step always stops the run
- Every step keeps its input, output and duration
From described routine to running routine, in one short video.
The routine described in your own words, the steps built and scheduled, the pause where money is at stake, and the trace of every run.
Read what the video shows
- Automate: routines that run themselves. Turn a repetitive routine into an automation that runs itself, on schedule or on a trigger.
- When something happens, Synapse does it for you. When something happens → Synapse does it for you.
- Describe the routine in your own words. Synapse builds the steps, checks and schedules.
- Every step, in order. Query data → Agent → Approval → Notification.
- On schedule, in your time zone. Daily, Weekly, Business days, Monthly or Interval.
- Workflow, agent or squad, now or on schedule. Run now, past runs under History → View run.
- Money involved? It pauses for you. Paused at the step, waiting for your approval.
- Approved? It runs. Rejected? Cancelled. Approve and continue or Reject, with the note in the history.
- Every run, with the full trace. Input, Output, duration and credits for each step.
- Less routine by hand. More decisions where it counts. Meet Synapse.
Monday morning, before and after
The same routine, with the same human decision in the middle. What changes is who does the work of getting to it.
Describe the routine once. Synapse runs it — and stops where you decide.
The Operations module turns repetitive processes into automations that run on their own and stop where someone needs to decide — with permissions, approval and a full trace of every run.
Thirteen step types
Actions, Integrations, Control and People: thirteen step types in four groups to build the routine the way it actually happens.
Runs on schedule or on a trigger
The automation runs on a schedule or when something happens — and goes on its own up to where the rule asks for a person.
Pauses where you decide
Money or risk involved? The run pauses at the step and waits for your approval before going on.
Role-based permissions
Never beyond the badge of whoever runs it: read, write or delete. Without permission, it stays blocked.
Full trace
Every run with input, output, duration and credits for each step — the proof of what ran, and why.
One routine, from the request to the end of the month
The same Monday, followed through the screens your team will use after creating the account.
Describe the routine the way you would explain it to someone
You draw nothing to begin with. You write in the chat what happens every Monday, and the routine is built, checked and scheduled. Anything that cannot be undone stops and asks you to confirm first.
- Built from a sentence written in plain language.
- Scheduled at the time you named.
- It stays a draft until you activate it, and a draft does not run.
Thirteen kinds of step, in four groups
The flow is visible on a canvas: every step is a box and every arrow is the order. The steps fall into Actions, Integrations, Control and People, and it is in the People group that the step which halts everything lives.
- An agent drafts, a condition picks the path, a query brings the number.
- A message goes out on the channel, a call reaches another system.
- The order is the arrows, and the editor warns you when a step is left unconnected.
The assistant never outranks the person running it
Every assistant is written in plain language, like a procedure for someone on their first day. What it may do is ticked in a catalog organized by area, with a tag saying whether that reads, changes or deletes.
- You tick the folders it may draw answers from.
- Whatever your own role forbids shows up blocked.
- You can test it with your hardest question before letting it loose.
The run stops where the rule needs a person
The human review step is not a notice that passes by: it suspends the run, notifies whoever decides, and only continues once someone approves. Rejecting cancels the whole run.
- The reviewer corrects what the AI proposed before releasing it.
- You can set a deadline and the rule that applies if no decision comes.
- With no reviewer named, the request has no owner and the process does not move.
Afterwards, the trace speaks for itself
Every run keeps the step sequence with the input, the output, the duration and the consumption of each one. When something fails, the step shows the exact error message.
- The input and output of each step, side by side.
- Consumption is recorded in credits, step by step.
- Re-run from the step that broke, without repeating what already worked.
At the end of the month, the routine explains itself
The renewal question is always the same: how many times did somebody still have to do this by hand? The platform answers without a new report.
- How many runs there were and how many succeeded.
- How long the routine took on average.
- How much it consumed, with the projection for the end of the month.
Starting takes an afternoon
- 1
Pick one routine that repeats
Just one, with an owner and a clear beginning and end. The one your team redoes every Monday is the obvious candidate.
- 2
Put the approval where the rule needs a person
Draw the steps and place the human review before anything that leaves the company or touches money. Name who decides while you are building it.
- 3
Activate it and follow the trace
Run it on demand a few times, then let the schedule fire it. Every run is recorded step by step.
One door: doing
Knowledge is knowing. Operations is doing.
Operations
For the operation that already knows which routine it wants off its hands.
The price of this offer is not published here yet. Create the account and we will talk it through before any charge.
- Routines that start on a click, on a schedule, on a call from another system or on a platform event
- Thirteen kinds of step, in four groups
- A human review step that halts the run until someone decides
- A per-step trace with input, output, duration and consumption
- Re-running from the step that failed
- Assistants bounded by what the role of the person running them allows
You create the account first and choose the plan afterwards.
No lock-in. Cancel whenever you like and keep using it until the end of the paid period.
What holds the operation together
- Four ways to startSomeone clicks, the schedule fires, another system calls in with a signed request, or something happened in here. Eight platform events of its own can set a routine going.
- The approval always haltsThe human review step suspends the run and notifies whoever decides. It is not a notice that passes by: nothing continues until someone approves.
- Everything is recordedThe input, output, duration and consumption of every step, and the exact error message when something fails.
- Reading is only readingThe platform reads the systems you connect and never changes or deletes anything at the source. Writing to another system is always a tool configured case by case.
On TVBluey, the company behind Synapse, on Globo NSC's TECH SC
Questions from whoever answers for the process
What if nobody approves?
The run stays stopped. The approval step always halts the process, and with no reviewer named the request has no owner. Name who decides while you build the step; you can set a deadline and the rule that applies if the decision never comes.
What makes a routine start?
Four things: someone clicks, the schedule fires, another system calls in with a signed request, or something happened in here. The events are the eight the platform actually emits, among them message received, lead created, transactions imported and data load finished.
Can I test it before leaving it on automatic?
Yes. Run it on demand as many times as you like before scheduling it. And a flow in draft does not run: not from the button, not from a schedule. Activating it is your decision.
And when a step fails?
The step shows the exact error message in the execution trace. You fix it and re-run from that step, without repeating what had already worked.
Do I need the Data offer to use this?
No. A routine can read a number through the query step, which carries up to 50 rows forward to the steps that follow. The data platform, with its catalog, metrics and notebooks, is a separate offer and is not included here.
Does the platform change my systems?
The sync only reads. It pulls data from your systems and never changes or deletes anything at the source. Writing to another system happens through a tool configured case by case, never through the reading.
Can a routine wait?
It can. A wait inside the flow runs straight through for up to 60 seconds; beyond that the run is suspended and resumed later, at the right time. For long pauses the way is a scheduled trigger.
Can I edit an automation that is already running?
You can. Runs in flight finish on the old version and the next ones use the saved version.
Pick the Monday routine
Start with the one your team redoes every week. If a month from now it is still being done by hand, we will say so before you ask.
Start with the Monday routine