Spondyr
for LuumenAI
Check correspondence status and send held batches, with approval on the delivery
Connect Spondyr and Luumen can read your correspondence setup the way you would: transaction types, templates, recipients, conditions, and the status of anything already generated. When a batch needs to go out, or a template rule needs to change, the write is previewed and held for approval first. Authentication is by API key.
The Spondyr toolbox
21 tools: 12 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadList ConditionsList all conditions for a transaction type.
- ReadList Event Types for Transaction TypeRetrieves all event types associated with a specific transaction type in Spondyr.
- ReadGet Spondyr StatusRetrieve the status of a previously generated correspondence.
- ReadGet Transaction TypesRetrieve a list of available transaction types.
- ReadGet RecipientRetrieve details of a specific recipient.
- ReadList RecipientsList all recipients for a transaction type.
- ReadGet Search FilterRetrieves details of a specific search filter in Spondyr by name and transaction type.
- ReadList Search FiltersList all search filters for a transaction type.
- ReadSearch CorrespondenceSearch for generated correspondence (spondyrs) by multiple criteria including batch ID, event type, and custom search filters.
- ReadGet TemplateRetrieve detailed configuration for a specific correspondence template.
- ReadList TemplatesList all templates configured for a transaction type.
- ReadGet Transaction TypeRetrieve details of a specific transaction type.
- WriteCreate ConditionCreate a condition rule for template selection in Spondyr. Approval by default
- WriteCreate Transaction TypeCreate a new transaction type. Approval by default
- WriteDeliver Spondyr correspondenceTrigger delivery of previously generated correspondence to recipients. Approval by default
- WriteUpdate Event TypeUpdate an existing event type name within a transaction type. Approval by default
- WriteDelete RecipientDeletes a recipient configuration from a transaction type in Spondyr. Approval by default
- WriteCreate Search FilterCreate a new search filter for a transaction type in Spondyr. Approval by default
- WriteDelete Search FilterDeletes a specific search filter from the Spondyr system. Approval by default
- WriteCreate Spondyr SSO stubCreate a one-time SSO user stub in Spondyr. Approval by default
- WriteUpdate Transaction TypeUpdates an existing transaction type's name and/or JSON schema in Spondyr. Approval by default
One prompt, start to finish
What a governed Spondyr run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create condition, create transaction type, deliver spondyr correspondence, update event type, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Spondyr — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut Spondyr to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.