Spondyr

@Spondyr show me all transaction types we've registered and their current search filters

Here are your registered transaction types in Spondyr: • **order_confirmation** – 3 active search filters (high_value_orders, international_shipments, rush_orders) • **invoice** – 2 active search filters (overdue_30days, net_terms) • **shipping_notification** – 1 active search filter (tracking_available) Each transaction type maps to a JSON schema you've defined. The search filters let you segment which template gets applied based on transaction data fields. Would you like details on any specific filter's conditions?

This read-heavy example shows how Spondyr organizes document generation rules. Useful for auditing your correspondence logic before making changes. Requires API key with read access to transaction types and filters; no side effects.

@Spondyr create a new recipient called 'billing_contact' for our invoice transaction type, mapped to the email field in our schema

Created recipient **billing_contact** for transaction type **invoice**. **Configuration:** • Recipient type: email • Data path: `transaction.billing_email` • Fallback: none (delivery will fail if field is missing) This recipient can now be referenced in your invoice templates. When you generate correspondence for an invoice transaction, Spondyr will extract the email address from `billing_email` in your JSON payload and send the rendered document there.

This write example demonstrates recipient mapping—a core Spondyr concept for routing generated documents. Creates a persistent configuration in your account. Ensure your transaction JSON schema includes the field you're mapping to, or deliveries will fail silently.

@Spondyr generate a summary of all conditions currently applied to our 'order_confirmation' templates and flag any that might overlap

Your **order_confirmation** transaction type has 5 active conditions across 3 templates: **Template: standard_order** • `order.total < 500` AND `order.country == 'US'` **Template: high_value_order** • `order.total >= 500` (potential overlap with international_order) **Template: international_order** • `order.country != 'US'` AND `order.total >= 500` (overlaps with high_value_order for international orders over $500) **Recommendation:** The high_value and international templates will both match for non-US orders ≥$500. Spondyr uses first-match logic, so international_order will never trigger. Consider adding `order.country == 'US'` to the high_value_order condition.

This synthesis example shows the AI reasoning over your Spondyr configuration to catch logic errors. Conditions control template selection, and overlaps cause silent failures. Requires read access to conditions and templates; the AI infers conflicts from rule precedence, not runtime logs.

When Spondyr fits multi-template deal workflows

A 6-person sales ops team closes 40-60 deals a month, each needing a custom contract pulled from 8 different templates depending on deal size, region, and payment terms. Spondyr's condition and filter tools let you encode those rules once, then generate the right PDF every time a deal moves to "Closed Won" in your CRM. The MCP's 21 tools handle the full loop: define transaction types for your deal schema, map recipients (customer, legal, finance), set conditions for template selection, and trigger delivery. This works when your template logic is stable and your deal data lives in structured JSON. If you're still experimenting with contract structure or your sales process changes weekly, the upfront schema and condition setup will slow you down. For teams with repeatable workflows and 5+ templates, Spondyr turns document generation into a background task.

Spondyr for high-volume welcome sequences

A 3-person customer success team onboards 200 new accounts a month, each requiring a welcome packet with 4-6 documents: terms of service, data processing agreement, implementation checklist, and a personalized setup guide. Spondyr's transaction type and recipient tools let you model each onboarding as a structured event, then auto-generate the full packet when the account hits "Active" status. The search filter tools help CS reps pull up past packets by account tier or signup date when a customer asks for a resend. This MCP shines when your onboarding docs are template-driven and your account data is clean. If your packets need heavy customization per customer or your team is still figuring out what to include, you'll spend more time tweaking conditions than generating docs. For teams doing 100+ onboardings a month with stable templates, Spondyr removes the manual assembly step.

When Spondyr handles recurring regulatory filings

A 4-person finance team files monthly compliance reports to 3 different regulators, each requiring a specific format and data subset from the same transaction ledger. Spondyr's condition and recipient tools let you define each regulator as a recipient with its own template and data filters, then trigger all three reports from a single monthly transaction event. The SSO stub tool lets you embed a secure link in your internal dashboard so the CFO can preview reports before delivery. This works when your reporting cadence is predictable and your data schema is locked. If your regulators change requirements mid-year or your transaction structure varies by region, the schema and condition updates become a maintenance burden. For teams filing the same reports every month with minimal variance, Spondyr turns a 2-day manual process into a 10-minute review.