← All products
Synapsi / Product / Tools

Give agents the right actions.Nothing more.

A tool is one approved action in software you already use: send an email, find a contact, open a task. You decide, for each agent, whether it runs by itself, waits for a person, or is refused.

See it work Open workspace
Tool policy · Energy Customer Carelive
knowledge.searchauto
comms.email.sendproposed
tasks.task.createapproval required
human.handoffauto
crm.contact.createdenied
A capability with no setting is denied.
How it works
01

Three modes, one default

Each tool is set to auto, approval required, or denied. A capability with no setting is denied, so nothing is allowed by accident.

02

Every proposal is recorded

The platform records every action an agent proposes, including the ones that were refused, in an append-only audit log.

03

Capabilities, not vendors

Workflows name what they need, such as sending an SMS, never who provides it. Connect your own accounts and swap a provider without rewriting a workflow.

What agents can reach

Your systems, one permission at a time.

Connections belong to your organisation and your accounts. A capability with nothing connected fails clearly instead of pretending to succeed.

Capabilities
comms.email.sendcomms.sms.sendcomms.whatsapp.sendcomms.template.sendcrm.contact.findcrm.contact.createtasks.task.createchat.message.sendknowledge.searchhuman.handoffconversation.replyhttp.request
Connected directly
Google WorkspaceMicrosoft 365OutlookWhatsApp BusinessTwilio SMS and WhatsAppSlackTelegramHubSpotClickUpMailchimpSMTPAny REST CRM
Through Composio
Google SheetsGoogle CalendarGoogle DriveSalesforceNotionStripeAirtableDocuSignMicrosoft TeamsSharePointZoom
Permissions at work · on the record

A billing question arrives in the service inbox.

Audit log · append-onlyrecording
#WhoWhat happenedResult
001Tool · knowledge.search · autoSearch what you know. knowledge.search "estimated reading"auto
002Tool · crm.contact.create · deniedTry something not allowed. crm.contact.create refuseddenied
003Tool · comms.email.send · approval requiredDraft the reply. proposed: email to customerawaiting approval
004Approvals · operatorApprove and run. approved → comms.email.send executedapproved
Written in the same step as the action itself.Nothing is edited afterwards.

Example run. Available actions depend on the accounts you connect and the modes you set.

Where it sits

Each layer adds to the one beneath.

Layer 04 of 06

Tools adds what agents may do.

Each action in your software is set to run by itself, wait for approval, or be refused. No setting means refused.

It stands on the 3 layers beneath it.

Built to be trusted

Safe by default, provable afterwards.

Refused unless you allow it

Every action an agent can take needs a setting from you. With no setting, the answer is no.

A person approves what matters

Anything you mark as sensitive stops and waits. One press approves it, and the record shows who pressed.

A log nobody can edit

Each action is written to an append-only audit log in the same step as the action itself, refusals included.

Triggers are signed

Requests from your systems are signed and verified before a workflow starts, and bursts beyond the ceiling are held.

Roles for your team

Viewer, operator and owner. People sign in with the Google or Microsoft account they already have.

Your figures stay your figures

No model rewrites a price or an invoice amount. Numbers are sent exactly as your system produced them.

Clear boundaries

What it does, and what it will not.

It does
  • Scopes each action to a specific connected account
  • Suggests a risk level, while your stored setting decides
  • Fails clearly when a capability has nothing connected
It does not
  • Allow anything by default
  • Hide refused actions: they are in the record too
  • Enforce a spending cap per workflow: spend is shown, not limited

Approve the actions. Keep the record.

Connect one account, set three modes, and see the first run.

Open workspaceTalk to the team