AI agent integrationSpondyr

Spondyr integration for multiplayer collaboration with AI agents using Claude Code or Codex

One governed connection your whole team and its AI agents can share, with approved actions and human review, so working in Spondyr never means pasting credentials into a prompt.

Request access See API details

CategoryDocuments & Forms

Use Spondyr from Claude Code

Bring Spondyr context into engineering work while Type keeps app access attached to the teammate and workspace.

Automate Spondyr with Codex

Let coding agents ask for the right app action, preserve conversation context, and keep humans in the approval loop.

Connect open agent workflows

Use Type as the collaboration layer around OpenClaw and other LLM workflows that need app access.

Documents & Forms

What the Spondyr integration exposes

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.

One connection, many teammates

Connect Spondyr once, then decide which teammates can use it for threads, automations, skills, and coding work.

Representative actions

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.

Connection

API and auth details

Spondyr presents itself as an API-driven platform for template-managed correspondence delivery. Public materials describe template-driven content generation and distribution for channels such as email, SMS, fax, and postal mail; the public site links to API resources, while detailed endpoint access appears to be handled through Spondyr customer resources.

Source: Type catalog metadata
Auth schemes: API key
API docs: https://spondyr.io/
Official site: https://spondyr.io/

Source links

FAQ

Questions people ask before connecting Spondyr

Can Claude Code use Spondyr?

Yes. Type lets an AI teammate use connected Spondyr actions from a governed workspace context, so Claude Code work can reference the app without copying credentials into a local prompt.

Can Codex work with Spondyr through Type?

Yes. Codex can collaborate through Type with app context, skills, and approved actions. The Spondyr catalog entry includes public integration details and example capabilities where available.

Is this the same as a Spondyr MCP server?

Type exposes connected app capabilities to AI teammates and coding agents through Type's integration layer. Teams use it when they want shared app access, human review, and teammate-level permissions around agent work.