Sanaf AI
Start free
Documents

Spondyr, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Spondyr account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Documents
  • Connects with a key
  • 21 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Spondyr is

Spondyr is a correspondence template management and distribution platform that enables developers to quickly integrate template-driven content delivery via API, supporting email, SMS, fax, and postal mail.

You paste in a key from your own Spondyr account. It is kept encrypted, and you can withdraw it from inside Spondyr whenever you like.

How a run works

One message in, the work done in Spondyr.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Spondyr. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Spondyr account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

21 tools it already has

What it can do in Spondyr

These are the ready-made tools your AI employee already has in Spondyr. It is not limited to them, but it never has to be taught these.

  • Create ConditionTool to create a new condition. use when defining detailed rules for template selection based on transaction data.
  • Create Search FilterTool to create a new search filter. use when you need to define a reusable filter for a specific transaction type.
  • Create Spondyr SSO stubTool to create a one-time sso user stub in spondyr. use after application authentication to generate a temporary sso token for embedding or redirecting users.
  • Create Transaction TypeTool to create a new transaction type. use after defining the json schema for your data to register it in spondyr.
  • Delete RecipientTool to delete or deactivate a specific recipient. use when you need to remove an existing recipient mapping in spondyr.
  • Delete Search FilterTool to delete or deactivate a specific search filter. use when you need to remove an existing search filter by name. call after confirming the filter exists.
  • Deliver Spondyr correspondenceTool to trigger delivery of a previously generated correspondence. use after calling the generate api.
  • Get RecipientTool to retrieve details of a specific recipient. use when you need to fetch recipient configuration for a given transaction type. example: "retrieve recipient 'customer' for trans
  • Get Search FilterTool to retrieve details of a specific search filter. use when you need to fetch the tag and transaction type of an existing filter by name.
  • Get Spondyr StatusTool to retrieve the status of a previously generated correspondence. use after generating correspondence to check its processing and delivery status.
  • Get TemplateTool to retrieve a specific template’s configuration and content reference. use when you need to inspect a template's settings for a transaction type. example: "fetch template 'myt
  • Get Transaction TypeTool to retrieve details of a specific transaction type. use when inspecting a transaction type schema. example: "get transaction type 'orderplaced' to view its json schema."
  • Get Transaction TypesTool to retrieve a list of available transaction types. use after authentication to discover data schemas.
  • List ConditionsTool to list all conditions for a transaction type. use when you need to retrieve all condition rules defined for a specific transaction type.
  • List Event TypesTool to list all event types for a given transaction type. use when you need to discover available events after retrieving transaction types.
  • List RecipientsTool to list all recipients for a transaction type. use when you need to discover or verify all configured recipients before sending or managing correspondence.
  • List Search FiltersTool to list all search filters for a transaction type. use when you need to discover available filters before searching correspondence.
  • List TemplatesTool to list all templates for a transaction type. use when you need to discover available templates before generating correspondence.
  • Search CorrespondenceTool to search generated correspondence by multiple criteria. use after correspondence generation to retrieve historical records with filters, paging, and sorting.
  • Update Event TypeTool to update an existing event type. use when you need to modify the name or associated transaction type of an event type. example: rename the 'ordershipped' event to 'orderdeliv
  • Update Transaction TypeTool to update an existing transaction type. use after retrieving a transaction type to apply changes. example: "update transaction type 'order' with new json schema."
Access, and who is in charge of it

You stay the boss of your Spondyr account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Spondyr account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Spondyr is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Spondyr and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Spondyr

Can an AI employee really work inside Spondyr?
Yes. It signs in to your own Spondyr account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Spondyr?
No. Nothing moves and nothing is replaced. Your records stay in Spondyr, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Spondyr account?
You paste in a key from your own Spondyr account. It is kept encrypted, and you can withdraw it from inside Spondyr whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Spondyr?
It has 21 ready-made tools in Spondyr today, among them Create Condition, Create Search Filter and Create Spondyr SSO stub. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Spondyr and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Spondyr and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Spondyr?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Spondyr is written down with what it did and when.