ConnectorSpondyr

Spondyr integration for Claude and Codex

Create a Spondyr connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.

Get started See API details

CategoryDocuments & Forms

Use Spondyr from Claude

Add the Spondyr connection to a Space that runs Claude, then use it from every channel in that Space.

Use Spondyr from Codex

Add the Spondyr connection to a Space that runs Codex, then use it from every channel in that Space.

Use Spondyr from Sidekick

Connect your own OpenClaw to Sidekick while Type provides the conversations, permissions, connections, skills, and automations.

Documents & Forms

What the Spondyr connector can do

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 Spaces

Connect Spondyr once, then decide which Spaces can use it in threads, skills, automations, 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 use Spondyr?

Yes. Add a Spondyr connection to a Space that runs Claude, then use its approved tools and data from any channel in that Space.

Can Codex work with Spondyr through Type?

Yes. Add a Spondyr connection to a Space that runs Codex, then use its approved tools and data from any channel in that Space.

Is this the same as a Spondyr MCP server?

Not exactly. Type uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.