Every automation HubPlus can run,
in one place.
Every automation is a trigger (something that happens in your stack) plus optional filters, delays and conditions, plus one or more actions HubPlus runs in response. Members feel the touch. You don't lift a finger.
54 triggers · 44 actions · 51 ready-made recipes — same catalog your admins see.
Automation
LiveWelcome new Luma RSVPs into Slack
Guest RSVPd (Luma)
Send Slack DMOnly continue if
ticket_type equals "Workshop"
The four building blocks
An automation is four primitives, stacked.
Trigger
The event that starts the automation — a member joining, an RSVP, a Stripe purchase, an inbox SLA breach, or the clock.
14 categories below, from Member Events to Commerce.
Filter
Narrow a trigger to a single Slack channel — single-select, searchable.
Applies to the two Slack channel triggers.
Delay
Wait before the next step. 1–365 minutes / hours / days, optional working-days-only that shifts Sat/Sun to Monday 09:00 UTC.
Presets: 5 min · 1 hour · 24 hours · 3 days · 1 week.
Only continue if
Stop the run unless rules built on the trigger's variables match. AND/OR logic, operators from equals to greater-than.
Use any variable the trigger emits, e.g. {{ticket_type}}.
There's also a Scheduled trigger (hourly / daily / weekly / monthly + timezone, working-days-only optional) for time-based automations that don't react to an event.
The catalog
Every supported trigger, action and recipe.
Grouped exactly the way your admins see them in the builder. Click any card to see what it emits or which inputs it needs.
Member Events
6Time-based
1Slack Events
4Native Inbox
4Native Discussions
1Events (Native)
11Events (Luma)
7Events (Eventbrite)
4Commerce
6Kit
6MailerLite
4How they stack
The real wins come from crossing tools.
Eventbrite → Slack → Kit tag
When a workshop ticket is bought on Eventbrite, wait ten minutes, DM the buyer the joining link, and apply a "Workshop attendee" tag in Kit so the next email segment finds them automatically.
Attendee RegisteredSend Slack DM
Apply Kit TagNew member → Slack welcome → Kit subscribe
The moment someone joins your community, ping them with a personal Slack DM from a chosen teammate and add them as a subscriber in Kit — primed for your next newsletter, automatically.
Send Slack DMAdd Subscriber (Kit)Native RSVP → Slack DM → MailerLite group
When a member RSVPs to a native event, wait a day, then send them a Slack reminder and drop them into the matching MailerLite group so post-event follow-ups land in the right list — no CSV exports.
Send Slack DM
Add to MailerLite GroupThe builder
From idea to running automation in under five minutes.
- 1
Pick a trigger
Browse the catalog and choose what event should start your automation — a member joining, an RSVP, an inbox SLA breach, a scheduled time.
- 2
Shape the flow
Drop filters, delays and conditions between trigger and actions. Drag actions in any order; the builder handles the rest.
- 3
Test, then enable
Run a test in the built-in tester with a real member as input, inspect the output, then flip it live. Pause anytime.
FAQ
Questions operators ask before turning automations on.
What's the difference between a trigger and an action?
A trigger is the event that starts an automation — something that happens in your stack (a Luma RSVP, a Slack reaction, a Stripe payment). An action is what HubPlus does in response (post to a channel, send a DM, refund an order, apply a Kit tag). One trigger, one or more actions.
Can one automation span two integrations?
Yes — that's most of the value. A Luma RSVP can trigger a Slack DM and apply a Kit tag in the same run. An Eventbrite registration can trigger a branded receipt email and drop the buyer into a MailerLite group. Any trigger pairs with any action your community has access to.
Do I need to write code?
No. Pick a trigger, drop in actions, optionally add filters / delays / conditions, hit save. Everything is a visual node in the builder.
How fast do automations run?
Instant triggers (webhooks like a new Slack post or a Stripe purchase) fire within seconds. Polling triggers (member inactive, event starting soon, low stock, inbox SLA) check on a clock — typically every few minutes. Scheduled automations run at the exact hour and minute you choose, in your timezone.
Can I test an automation before turning it on?
Yes. Every automation has a built-in tester — pick a real member or record as the input, run the flow, and inspect each step's output before you flip it live.
Where do I build them?
Inside your Hub, under Automations. Each community has its own builder, templates and run history.
Create your Hub.
Free to start.
Free to start · upgrade when you outgrow it · cancel anytime. Bring your community in minutes.