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
  • When To Create Multiple Workflows
  • Workflow Status (Lifecycle)
  • Types and Variants
  • Invoice workflows
  • Payment workflows
  • Operational Guidance
  • API reference

Workflows

Was this page helpful?
Previous

Workflow Triggers

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.

A workflow is the configuration that decides:

  • What event to react to (invoice or payment).
  • Which customers it applies to.
  • What should happen (actions).

When To Create Multiple Workflows

Create multiple workflows when:

  • you need different messaging per segment (for example enterprise vs SMB)
  • you want separate cadence rules (different reminder schedules)
  • you want different senders/templates per billing entity

Workflow Status (Lifecycle)

In practice, statuses support a safe rollout:

  • Draft: build the workflow configuration.
  • Inactive: ready, but not running yet.
  • Active: running in production.
  • Archived: permanently disabled.

Types and Variants

Invoice workflows

Use invoice workflows for invoice delivery and dunning.

  • Invoice becomes final: email the invoice (often with PDF attached).
  • Invoice overdue: send reminder emails after due date.

Payment workflows

Use payment workflows to notify customers about payment issues.

  • Failed payment: send an email when a payment attempt fails.

Operational Guidance

  • Name workflows based on the customer-facing intent (for example: “Invoice Final Delivery” or “Overdue Reminder 7/15/30”).
  • Keep the number of active workflows small and intentional. If you need lots of variants, standardize templates.
  • If your workflow includes a pay link, validate your payment setup first (PSP integration + payment acceptor).

API reference

  • List workflows
  • Create a workflow
  • Update a workflow
  • Activate a workflow
  • Deactivate a workflow
  • Archive a workflow