Spondyr MCP integration
Tracks whether generated correspondence was delivered, triggers delivery, and maintains the template conditions and transaction schemas behind it.
21actions available
Three actions you can hand over today
Every action runs live through MCP. Nothing to build, nothing to maintain.
Search correspondence
Lyro searches generated correspondence by batch ID, event type, and filters. Agents locate specific documents without browsing archives.
Create search filter
Lyro creates a new search filter to organize correspondence queries. Agents set up saved searches for recurring document lookups.
Deliver spondyr correspondence
Lyro triggers delivery of generated documents to recipients. Agents send prepared correspondence without manual steps.
How businesses use Spondyr + Lyro
Each card is one request a support team gets, and the Spondyr actions Lyro runs to close it.
Confirm a document actually reached the customer
Lyro searches correspondence by batch ID, event type, or a custom filter, then reads the processing and delivery status on the specific item in question.
Search CorrespondenceGet Spondyr StatusList Search FiltersRelease correspondence that was held for review
Lyro checks the template's configured delivery methods and recipients, then triggers delivery of a document that was generated but not yet sent.
Get TemplateList RecipientsDeliver Spondyr CorrespondenceChange which template a transaction gets
Lyro reviews the condition rules already defined for a transaction type, adds a new matching rule on a data field, and audits the templates those rules point at.
List ConditionsCreate ConditionList TemplatesKeep the transaction schema in step with the data
Lyro inspects a transaction type's JSON schema and CSV field mappings, updates it when fields are added or renamed, and reviews the event types defined against it.
Get Transaction TypeUpdate Transaction TypeList Event Types For Transaction Type
How it works
Get started in 3 steps
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Spondyr actions it has and picks the ones a request needs.
Connect Spondyr
Authorize the Spondyr account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Spondyr actions that close it and chains as many as the request needs.
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free
Spondyr · Lyro
What can you do in Spondyr without me setting anything up?
These, right away:
- Create condition
- List conditions
- Update event type
Great, let's start with the first one.
FAQ
Everything else about Spondyr
Setup, permissions, and the limits of what Lyro can do inside Spondyr.
So correspondence can be produced and checked before it goes out. A document created with the generate-only flag waits until Deliver Spondyr correspondence triggers the actual send to its configured recipients, and Get Spondyr Status reports where a piece has got to in processing and delivery.
Every action available in Spondyr
All 21 actions your agent can call on Spondyr, straight from the live MCP connection.
List conditions
List all conditions for a transaction type.
Create condition
Create a condition rule for template selection in Spondyr.
Create transaction type
Create a new transaction type.
Deliver spondyr correspondence
Trigger delivery of previously generated correspondence to recipients.
Update event type
Update an existing event type name within a transaction type.
List event types for transaction type
Retrieves all event types associated with a specific transaction type in Spondyr.
Get spondyr status
Retrieve the status of a previously generated correspondence.
Get transaction types
Retrieve a list of available transaction types.
Delete recipient
Deletes a recipient configuration from a transaction type in Spondyr.
Get recipient
Retrieve details of a specific recipient.
List recipients
List all recipients for a transaction type.
Create search filter
Create a new search filter for a transaction type in Spondyr.
Delete search filter
Deletes a specific search filter from the Spondyr system.
Get search filter
Retrieves details of a specific search filter in Spondyr by name and transaction type.
List search filters
List all search filters for a transaction type.
Search correspondence
Search for generated correspondence (spondyrs) by multiple criteria including batch ID, event type, and custom search filters.
Create spondyr sso stub
Create a one-time SSO user stub in Spondyr.
Get template
Retrieve detailed configuration for a specific correspondence template.
List templates
List all templates configured for a transaction type.
Get transaction type
Retrieve details of a specific transaction type.
Update transaction type
Updates an existing transaction type's name and/or JSON schema in Spondyr.
The tools Spondyr sits next to
Same connection, same setup. Pick the next one your team already uses.
Basin
Reads and filters form submissions, creates and configures forms with spam protection, and wires webhooks to forward each entry.
Detrack
Answers delivery status from a DO number and date, corrects addresses and instructions before dispatch, and books collection jobs.
Formsite
Reads the form catalog, question labels, submission results, and webhook configuration for any Formsite form on request.
Make
Provisions organizations, reports operations usage, triggers password resets, and answers plan questions from live Make data.
Proxiedmail
Stands up webhook receivers for incoming mail, checks the payloads they captured, and repoints existing proxy bindings.
TinyFish MCP
Starts browser automation runs from a plain-language goal, polls them to completion, cancels the ones that should stop, and returns step screenshots.
Ready to connect Spondyr?
Authorize the account and your agent has all 21 actions from the first conversation.