Workflows
🚧 Under development
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).