Spondyr

21 tools available

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.

documents email

Connect Spondyr Visit Spondyr ↗

Connect Spondyr to Definable to auto-index uploads, answer questions over a doc set, extract structured fields from contracts. Personas call Spondyr's 21 tools directly from chat or scheduled flows. Connect this integration to a knowledge persona — the agent will ground answers in your documents with citations.

Common workflows with Spondyr

Auto-index new files

Watch for new uploads
Chunk, embed, and index
Make queryable via your knowledge persona

Q&A against a folder

Pin a folder as a brain
Ask the persona questions
Returns answers with citations

Document-trigger flows

New contract uploaded
Persona extracts key terms
Routes to the right approver

Spondyr actions 21

Every Spondyr action below is a callable tool any Definable persona can invoke.

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.

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.

Create Transaction Type

Tool to create a new transaction type. Use after defining the JSON schema for your data to register it in 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.

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.

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.

Get Spondyr Status

Tool to retrieve the status of a previously generated correspondence. Use after generating correspondence to check its processing and delivery status.

Get Transaction Types

Tool to retrieve a list of available transaction types. Use after authentication to discover data schemas.

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.

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

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.

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.

Delete Search Filter

Deletes a specific search filter from the Spondyr system. Use this when you need to remove a search filter that is no longer needed. Both the filter name and transaction type must exactly match the values used when the filter was created. If the filter does not exist, the API will return an error.

Get Search Filter

Retrieves details of a specific search filter in Spondyr by name and transaction type. Returns the filter's name, tag value, and associated transaction type. Use this when you need to look up an existing search filter's configuration, verify its tag format, or confirm which transaction type it belongs to before using it for correspondence searches.

List Search Filters

Tool to list all search filters for a transaction type. Use when you need to discover available filters before searching correspondence.

Search Correspondence

Search for generated correspondence (spondyrs) by multiple criteria including batch ID, event type, and custom search filters. Returns paginated results with delivery status, recipient information, and URIs to access generated documents. Use this to find and retrieve previously generated correspondence.

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 Template

Retrieve detailed configuration for a specific correspondence template. Returns template content reference ID, event type, recipients, delivery methods, conditions, and search filters. Use this action when you need to: - Inspect template settings and configuration - View recipient delivery methods (Email, Mail, Text, DocuSign, Fax, Destination) - Review template selection conditions and search filters - Get the template content reference ID for correspondence generation Prerequisites: Use 'Get Transaction Types' to discover transaction types, then 'List Templates' to find available template names. Example: Retrieve template 'OrderConfirmationEmail' for transaction type 'CustomerOrder'.

List Templates

List all templates configured for a transaction type. Use this to discover available templates before generating correspondence or to audit template configurations. Returns template metadata including name, event type, content type, recipients, conditions, and search filters. Use Get Template action to retrieve full template content and detailed configuration.

Get Transaction Type

Tool to retrieve details of a specific transaction type. Use when inspecting a transaction type schema. Returns the schema definition including JSON structure and CSV field mappings. Example: "Get transaction type 'CustomerOrder' to view its JSON schema and available fields."

Update Transaction Type

Updates an existing transaction type's name and/or JSON schema in Spondyr. Use this tool to: - Modify the JSON schema/template of a transaction type to add, remove, or change data fields - Rename an existing transaction type - Update sample data values in the template Prerequisites: The transaction type must already exist. Use 'Get Transaction Types' to list available types or 'Get Transaction Type' to retrieve the current schema before updating. Example: Update the 'OrderPlaced' transaction type with a new JSON schema that includes customer address fields.

Frequently asked questions

What can I automate with Spondyr on Definable?

Anything Spondyr exposes through its API. Common documents workflows on Definable include auto-index uploads, answer questions over a doc set, extract structured fields from contracts. Personas can call any of the 21 Spondyr tools directly, then chain the result into another integration without you writing code.

How does Spondyr authentication work?

Spondyr uses API_KEY on Definable. You connect once from the integrations page, scoped to the permissions you choose, and from then on any persona that has the integration enabled can act on your behalf. Tokens are encrypted at rest and rotated automatically.

Is the Spondyr integration included in my Definable plan?

Yes — every Definable plan, including Starter, includes access to all 21 Spondyr tools. You only need a separate Spondyr subscription if Spondyr itself charges per seat or per API call.

Is using Spondyr through Definable secure?

Every call from a persona to Spondyr is logged with the user, persona, prompt, and response. Tokens never leave Definable's secrets vault, scopes are configurable per persona, and you can revoke access at any time from the integration page.

How do I get started with Spondyr on Definable?

Sign up for Definable, open the integrations page, find Spondyr, and connect via OAuth or API key. You can immediately attach Spondyr to any persona and start running workflows. The free Starter plan includes 5,000 credits/month.

What Spondyr actions does Definable expose?

Definable exposes all 21 Spondyr actions as callable tools — including `List Conditions`, `Create Condition`, `Create Transaction Type`, plus 18 more. Each tool gets a typed parameter schema so personas know exactly how to call it.

Ready to automate with Spondyr?

Wire it up in minutes. No coding required.

Start for free Schedule a demo

← All integrations