ceven

Spondyr

Triggers multi channel correspondence across email, SMS, and print, manages template logic based on transaction data, and tracks delivery status in real time.

Try Spondyr in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Spondyr integration

    • Describe the outcome and Ceven picks the right Spondyr calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Spondyr data, across all 21 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Spondyr access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Spondyr, when, and on whose behalf.
    • The agent pauses and asks when Spondyr is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Spondyr.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Spondyr action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Spondyr, and when to use it.

Deliver correspondence
Use this to trigger the actual delivery of a previously generated correspondence to the recipient.
Get status
Pull the processing and delivery status of a specific piece of generated correspondence.
Search correspondence
Query historical correspondence records using filters, paging, and sorting to find specific deliveries.
Create transaction type
Register a new transaction type in Spondyr after defining the JSON schema for your data.
Get transaction types
Pull a list of all available transaction types to discover valid data schemas.
List templates
Retrieve all available templates for a specific transaction type before generating content.
Get template
Fetch the configuration and content reference for a specific template by name.
Create condition
Define detailed rules for which template to select based on the transaction data provided.
List conditions
Retrieve all condition rules currently defined for a specific transaction type.
List event types
Discover all available event types associated with a given transaction type.
Update event type
Modify the name or associated transaction type for an existing event type.
List recipients
Pull all configured recipients for a transaction type to verify delivery targets.
Get recipient
Fetch the specific recipient configuration for a given transaction type.
Delete recipient
Remove or deactivate a specific recipient mapping in the Spondyr system.
List search filters
Pull all available search filters for a transaction type to prepare a query.
Create SSO stub
Generate a one time SSO user stub to allow temporary user access for embedding.
Deliver Spondyr correspondence
Tool to trigger delivery of a previously generated correspondence. use after calling the generate api.
Get Spondyr Status
Tool to retrieve the status of a previously generated correspondence. use after generating correspondence to check its processing and delivery status.
Create Search Filter
Tool to create a new search filter. use when you need to define a reusable filter for a specific transaction type.
Delete Search Filter
Tool 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.
Get Search Filter
Tool 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.
Create Spondyr SSO stub
Tool 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.
Get Transaction Type
Tool 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."
Update Transaction Type
Tool to update an existing transaction type. use after retrieving a transaction type to apply changes. example: "update transaction type 'order' with new json schema."

24 actions · scroll to see them all

Frequently asked questions

Ceven uses the Spondyr conditions engine to ensure the right message reaches the right person. When a workflow triggers, the agent passes the transaction data to Spondyr, which evaluates the predefined conditions to select the correct template. Ceven can manage these conditions via the API, allowing you to update the logic for which template fires based on data values without changing the workflow itself. This means if a legal requirement changes for a specific state, you update the condition in Spondyr and the agent automatically follows the new rule for all subsequent deliveries.
Yes. Ceven utilizes the Get Spondyr Status tool to poll the delivery state of any piece of correspondence. For postal mail, Spondyr provides updates as the document moves through the print and mail house. The agent can be configured to watch for a specific status transition, such as moving from generated to delivered. If a document fails to process or is returned as undeliverable, Ceven can trigger a fallback workflow, such as sending an automated email or alerting a customer service representative to update the address.
Transaction types act as the data contract between your system and the templates. Ceven can create and update these types using the API, ensuring that the JSON schema matches the data your business processes. When you define a new transaction type, you are essentially telling Spondyr what fields to expect, such as customer name or account balance. The agent ensures that every single request sent to Spondyr adheres to this schema to prevent delivery failures caused by missing or malformed data fields.
Yes. Ceven can call the Create Spondyr SSO stub tool to generate temporary access tokens. This is particularly useful for internal dashboards where you want to embed a Spondyr view or redirect a staff member to a specific template without requiring them to log in separately. The agent handles the request to create the stub and provides the resulting token to your application, creating a seamless transition for your users while maintaining the security of your main Spondyr account credentials.
Ceven implements a robust retry logic with exponential backoff to handle API fluctuations. It is important to note that Spondyr employs strict rate limits based on your account tier, which can lead to 429 errors during massive bulk sends. When the agent encounters a rate limit, it pauses the workflow and queues the remaining correspondence for delivery over a longer window. This prevents data loss and ensures that your communication stream remains steady without crashing your integration or triggering a permanent block from the Spondyr gateway.
Absolutely. The agent can list, get, and delete recipients for any given transaction type. Since Spondyr decouples the transaction from the delivery channel, Ceven can manage how a single event maps to multiple recipients. For example, one transaction can be configured to send a PDF to a customer email and a physical letter to a home address. Ceven monitors these recipient mappings to ensure that updates to customer contact preferences are mirrored in the Spondyr configuration in real time.
Ceven uses the Search Correspondence tool combined with reusable search filters. Instead of pulling every record and filtering locally, the agent defines a filter on the Spondyr side and executes a targeted query. This allows the agent to quickly find all correspondence sent to a specific user or all letters sent within a certain date range. The results are paginated, meaning the agent will automatically walk through multiple pages of results to compile a full report or audit trail for your compliance needs.
Ceven focuses on the management and triggering of templates rather than the visual design of the documents. While the agent can list templates, retrieve their configurations, and set up the conditions for their selection, the actual HTML or document layout is typically handled within the Spondyr web interface by designers. Once the template is created and named in the dashboard, the agent can immediately begin using it by referencing the template name in the delivery workflow, bridging the gap between design and execution.

Alternatives to Spondyr

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Lob logoLobSendGrid logoSendGridTwilio logoTwilio

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Spondyr and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free