# Spondyr AI integration on Definable

> 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.

## What this connects

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.

Vendor: https://www.spondyr.io

## Tools available

**21** tools available. First 12:

- `SPONDYR_CONDITIONS_LIST` — List Conditions — Tool to list all conditions for a transaction type. Use when you need to discover existing condition rules before creating templates or generating correspondence. Conditions define criteria for selecting specific templates based on transaction data.
- `SPONDYR_CREATE_CONDITION` — Create Condition — Create a condition rule for template selection in Spondyr. Conditions define matching criteria on transaction data fields that determine which document template to use. For example, create a condition on an 'OrderStatus' field to trigger different email templates for 'Pending' vs 'Shipped' orders.
- `SPONDYR_CREATE_TRANSACTION_TYPE` — Create Transaction Type — Tool to create a new transaction type. Use after defining the JSON schema for your data to register it in Spondyr.
- `SPONDYR_DELIVER_SPONDYR` — Deliver Spondyr correspondence — Trigger delivery of previously generated correspondence to recipients. Use this action after generating correspondence (via POST /Spondyr with IsGenerateOnly=true) to actually deliver the documents via email, fax, mail, or text message. The ReferenceID from the generate request is required to identify which correspondence to deliver.
- `SPONDYR_EVENT_TYPE_UPDATE` — Update Event Type — Tool to update an existing event type name within a transaction type. Use when you need to rename an Event Type. Example: Rename the 'OrderShipped' event to 'OrderDelivered' within the 'CustomerOrders' transaction type. Note: This only changes the event type's name - it does not move the event to a different transaction type.
- `SPONDYR_GET_EVENT_TYPES` — List Event Types for Transaction Type — Retrieves all event types associated with a specific transaction type in Spondyr. Event types define the kinds of events that can occur for a transaction type (e.g., "Created", "Updated", "Cancelled" events for an "Order" transaction type). Use this action after retrieving transaction types to discover what event types are available for a given transaction type. This is essential for understanding the event-driven workflows and setting up event-based automation in Spondyr. Returns an empty list if the transaction type exists but has no event types configured.
- `SPONDYR_GET_SPONDYR_STATUS` — Get Spondyr Status — Tool to retrieve the status of a previously generated correspondence. Use after generating correspondence to check its processing and delivery status.
- `SPONDYR_GET_TRANSACTION_TYPES` — Get Transaction Types — Tool to retrieve a list of available transaction types. Use after authentication to discover data schemas.
- `SPONDYR_RECIPIENT_DELETE` — Delete Recipient — Deletes a recipient configuration from a transaction type in Spondyr. Recipients are configured delivery endpoints (email addresses, fax numbers, physical addresses) that determine where correspondence will be sent when a transaction is processed. This action permanently removes a recipient configuration from the specified transaction type. Before deletion, use the 'List Recipients' action to verify the recipient name and transaction type. After successful deletion, the recipient will no longer be available for correspondence delivery.
- `SPONDYR_RECIPIENT_GET` — Get Recipient — Tool 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 transaction type 'OrderPlaced'."
- `SPONDYR_RECIPIENTS_LIST` — List Recipients — Tool to list all recipients for a transaction type. Use when you need to discover or verify all configured recipients before sending or managing correspondence.
- `SPONDYR_SEARCH_FILTER_CREATE` — Create Search Filter — Create a new search filter for a transaction type in Spondyr. Search filters enable you to define searchable fields within your transaction data. Once created, these filters allow you to quickly search and retrieve specific transactions based on field values (e.g., search by OrderID, CustomerName, InvoiceNumber). Use this tool when you need to make a specific field searchable within a transaction type.

## Auth

Auth schemes: `API_KEY`.

## How agents use Spondyr

Inside a Definable workflow, Spondyr is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Spondyr** — the Researcher (GPT-5.5) pulls context from Spondyr (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Spondyr** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Spondyr (create record, post message, draft email).
- **Designer / Engineer → Distributor → Spondyr** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Spondyr (attach file, open PR comment, post status).

The Verifier checks every Spondyr call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- documents — https://definable.ai/apps/category/documents/
- email — https://definable.ai/apps/category/email/

## Related

- HTML page: https://definable.ai/apps/spondyr/
- Same category (documents): https://definable.ai/apps/category/documents/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt