Bird + Memtro

Only when you ask, and only what it has been granted: send an SMS to a phone number (costs money, the recipient is texted); send an email now or at a set time (the recipients are emailed); cancel a scheduled email before it sends; create an email broadcast as a draft (nothing is sent); send or schedule a broadcast (everyone in its audience is emailed); cancel a scheduled or sending broadcast; create a contact; edit a contact; delete a contact (permanent); add contacts to an audience; remove a contact from an audience; suppress an email address so nothing more is sent to it; assign, label, resolve or mark read a WhatsApp conversation. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

Workspace API key. In the Bird dashboard, open Platform tools → API keys → Create and name it Memtro. Grant the read scopes, the write scopes for the actions you want, and webhooks write if Memtro should register its own webhook.

Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Bird for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.