- Setup
- 50 minutes
- Tested with
- n8n 1.90+
- File
- 26.3 KB
- Revision
- 1.0.0
The entry, in plain prose.
A SaaS lifecycle workflow that watches trial expiry, segments users by activation events, and sends timed nudges.
How it runs.
- 01.
Intake
Postgres receives the inbound payload. Schema validation runs first; failures are surfaced rather than silently dropped, so you never lose context to a malformed webhook.
- 02.
Enrichment
Customer.io → Slack performs deduplication, enrichment, and routing logic. Each step is idempotent; transient retries are safe by design.
- 03.
Routing
Owner routing applies a round-robin fallback when no explicit assignment exists. Holiday-mode flags and on-call schedules are respected where the source system surfaces them.
- 04.
Delivery
Schedule Trigger commits the result. Errors past this point alert via Slack with the failing payload attached; downstream systems never see partial state.
Indexed tools.
- Postgres
- Customer.io
- Slack
- Schedule Trigger
License.
| Tier | Seats | Resale | Price |
|---|---|---|---|
| Single Product | 1 | Not permitted | $59.00 |
| Growth Team | 5 | Not permitted | $119.00 |
Tested through twelve client deployments before archival. Setup consistently lands under 50minutes when integrations are pre-authorised. Recovers from upstream failures without intervention.