For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
LoginSandbox
Platform GuidesAPI DocsSDKMCP ServerChangelog
Platform GuidesAPI DocsSDKMCP ServerChangelog
  • Getting started
    • Introduction
    • Concepts
    • Onboarding guide
  • Use cases
    • Monetizing an AI agent
    • Pricing models for AI products
    • Configuring entitlements for AI products
  • Usage metering & events
    • Meters
    • Usage events
    • Unmatched events
    • Event reprocessing
  • Products & plans
    • Product Catalog
    • Pricing Plans
    • Features & Entitlements
  • Wallets & credits
    • Credit types & wallets
    • Credits in pricing plans
  • Customers & subscriptions
    • Customers
    • Subscriptions
    • Quotes
  • Invoicing
    • Invoices
    • Invoice corrections
    • Payment Collections
    • Tax
    • Currencies & Exchange rates
    • E-invoicing
  • Analytics & reporting
    • Insights
    • Report downloads
    • Revenue Recognition & Deferred Revenue
  • Integrations
    • CRM
    • ERP
    • Email Providers
    • Data Imports: Event File Uploads
    • Data Exports
    • Payment Service Providers
  • Settings & admin
    • Billing entities
    • Payment Options
    • User management
    • Customising invoices
    • Custom fields
    • Default platform settings
    • API key creation
    • Alert Rules
    • Workflows
  • Workflows
    • Workflow Triggers
    • Workflow Actions
    • Monitoring and Audit
    • Common Use Cases
  • For developers
    • Introduction
    • Authentication
    • Local development setup
    • API
    • Errors
    • Troubleshooting
    • Query Parameters
    • Expanding Responses
    • Idempotency
    • Timestamp formatting
    • Webhooks
    • Locale
    • MCP Server
LoginSandbox
On this page
  • Persona: Billing Ops (Invoice Delivery)
  • Persona: Finance Ops (Overdue Reminders / Dunning)
  • Persona: Customer Success (Failed Payment)
Workflows

Common Use Cases

Was this page helpful?
Previous

Introduction for developers

Next
Built with

Workflows are under active development and not yet generally released. The UI and API may change without notice. If you want early access, contact Solvimon support.

These are the most common workflows operators set up in production.

Persona: Billing Ops (Invoice Delivery)

Goal: customers automatically receive the invoice when it becomes final.

What good looks like:

  • invoice goes final
  • customer receives an email quickly (or within a configured window)
  • PDF is attached and matches the invoice

Related guides: Mailgun

API reference: Workflows, Workflow actions

Persona: Finance Ops (Overdue Reminders / Dunning)

Goal: reduce manual chasing by sending reminders at consistent intervals.

Typical cadence:

  • 7 days after due date
  • 15 days after due date
  • 30 days after due date

What good looks like:

  • reminders are spaced correctly
  • only unpaid invoices are included
  • messaging is consistent

Related guides: Mailgun

API reference: Workflows

Persona: Customer Success (Failed Payment)

Goal: when payment fails, notify the customer and guide them to resolution.

What good looks like:

  • customer understands what failed
  • customer has a clear next step (pay invoice, update payment method, contact support)

Related guides: Payment Collections

API reference: Workflows