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.
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. On Nagent, Spondyr is exposed as a fully-configurable documents integration that any agent can call — 21 actions, and API key authentication. No code is required to wire Spondyr into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Spondyr to automate the kinds of tasks documents teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Spondyr into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Spondyr, with input parameters and output schema. Drop these into any step of an agent built in Helix.
SPONDYR_CONDITIONS_LISTTool 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.
Input parameters
The name of the Transaction Type whose conditions are to be listed. Use the Get Transaction Types action first to discover available transaction types.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_CREATE_CONDITIONCreate 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.
Input parameters
A unique name identifier for this condition rule. Used to reference this condition when configuring template selection logic.
The data field from the transaction to evaluate. For nested fields, use underscore notation (e.g., 'Address_City'). Must exist in the transaction type's schema.
Optional list of allowed values for this field, separated by newlines. If provided, the condition will match only when the field value is in this list. Omit to allow any value.
The name of an existing Transaction Type to create this condition rule for. Must match a Transaction Type previously created in the system.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_CREATE_TRANSACTION_TYPETool to create a new transaction type. Use after defining the JSON schema for your data to register it in Spondyr.
Input parameters
The name of the Transaction Type to create
JSON-formatted string containing sample data defining the transaction schema
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_DELIVER_SPONDYRTrigger 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.
Input parameters
Templates to deliver; 'All' or comma-delimited list. Defaults to 'All'.
The unique reference ID returned from the original generate request (POST /Spondyr). Used to identify which correspondence to deliver.
Additional recipients beyond the originally configured list.
Original recipients to deliver; 'All', 'None', or comma-delimited list. Defaults to 'All'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_EVENT_TYPE_UPDATETool 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.
Input parameters
The new name for the Event Type.
The name of the existing Event Type to update.
The Transaction Type name this Event Type belongs to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_GET_EVENT_TYPESRetrieves 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.
Input parameters
The exact name of the Transaction Type whose event types are to be listed. Must match an existing transaction type name (case-sensitive).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_GET_SPONDYR_STATUSTool to retrieve the status of a previously generated correspondence. Use after generating correspondence to check its processing and delivery status.
Input parameters
Optional viewer last name for logging
Optional viewer first name for logging
Include original data payload in the response if true
Reference ID returned from the Send/Generate request
Optional user identifier for viewer context logging
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_GET_TRANSACTION_TYPESTool to retrieve a list of available transaction types. Use after authentication to discover data schemas.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_RECIPIENT_DELETEDeletes 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.
Input parameters
The name of the recipient to delete. This is the 'Name' field that was used when the recipient was created. Use the 'List Recipients' action with the transaction type to find all configured recipient names.
The name of the Transaction Type that the recipient belongs to. Must match an existing transaction type in your Spondyr account. Use the 'Get Transaction Types' action to list all available transaction types, or 'List Recipients' to see which transaction types have configured recipients.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_RECIPIENT_GETTool 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'."
Input parameters
The name of the Recipient to retrieve.
The name of the Transaction Type this Recipient is for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_RECIPIENTS_LISTTool to list all recipients for a transaction type. Use when you need to discover or verify all configured recipients before sending or managing correspondence.
Input parameters
The name of the Transaction Type whose recipients are to be listed. Use the Get Transaction Types action to retrieve available transaction type names.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_SEARCH_FILTER_CREATECreate 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.
Input parameters
The tag template defining which field from the transaction data to filter by. Use curly braces to wrap field names (e.g., {FieldName}). For nested fields, use underscore notation (e.g., {Vendor_Name}).
The name/identifier for this search filter. This will be used to reference the filter and is returned as ReferenceID in the response.
The name of the Transaction Type this search filter belongs to. Must be an existing transaction type name (use Get Transaction Types to retrieve available types).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_SEARCH_FILTER_DELETEDeletes 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.
Input parameters
The name of the Search Filter to delete. Must exactly match the 'Name' field used when the filter was created.
The Transaction Type that the Search Filter belongs to. Must exactly match the 'TransactionType' the filter was created with.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_SEARCH_FILTER_GETRetrieves 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.
Input parameters
The name of the Search Filter to retrieve (case-sensitive).
The name of the Transaction Type that the Search Filter belongs to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_SEARCH_FILTERS_LISTTool to list all search filters for a transaction type. Use when you need to discover available filters before searching correspondence.
Input parameters
The name of the Transaction Type whose search filters are to be listed
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_SEARCH_SPONDYRSSearch 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.
Input parameters
Page number for pagination (1-based).
Number of records per page (max 250).
Filter results to correspondence generated for a specific event type (e.g., 'NewOrder', 'Invoice', 'Receipt').
Sort direction: ASC or DESC.
Name of a custom search filter/tag to apply (e.g., 'OrderNumber', 'CustomerID'). Use with SearchValue to filter by custom metadata.
Field name to sort results by (e.g., 'CreatedDate', 'ReferenceID'). Defaults to 'CreatedDate' if not specified.
Value to match for the custom search filter specified in SearchName. Must be used together with SearchName.
Filter results to a specific batch reference ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_SSO_STUBTool 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.
Input parameters
Stub user's permissions. One of: Owner, Integrator, Editor, Tenant User.
SSO user's last name (URL-encoded).
Display timezone (IANA/Windows name). Defaults to UTC if omitted or invalid.
SSO user's first name (URL-encoded).
Tenant token for multi-tenant applications.
Your system's user identifier for the SSO user (URL-encoded).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_TEMPLATE_GETRetrieve 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'.
Input parameters
The name of the template to retrieve. Use the 'List Templates' action first to discover available template names for the transaction type.
The name of the Transaction Type this template belongs to. Use the 'Get Transaction Types' action to discover available transaction types.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_TEMPLATES_LISTList 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.
Input parameters
The name of the Transaction Type whose templates are to be listed. Use the Get Transaction Types action first to discover available transaction types.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_TRANSACTION_TYPE_GETTool 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."
Input parameters
The name of the Transaction Type to retrieve. API is case-insensitive.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SPONDYR_TRANSACTION_TYPE_UPDATEUpdates 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.
Input parameters
The new or updated name for the transaction type. Use the same value as TransactionType to keep the name unchanged, or provide a different value to rename it.
A valid JSON-formatted string defining the transaction schema with all available properties and sample data. This defines what data fields are available for correspondence templates.
The name of the existing transaction type to update. This identifies which transaction type to modify.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 47 agents privately built on Nagent that already use Spondyr.
Build on Nagent
Connect Spondyr to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Spondyr, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Spondyr is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Spondyr is connected, you configure its 21 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Spondyr steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Spondyr event fires, the agent kicks off automatically.
Every Spondyr action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Spondyr ships with 21 pre-built documents actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Spondyr together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Spondyr-based workflows tailored to your business.