A brief becomes a real page.Prepare FunnelKit automations and broadcasts
Build an inactive automation and review a broadcast before anything is sent.
Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- EMCP Pro 3.19.0+, active FunnelKit Automations and administrator access.
- A practice site with test contacts; Automations Pro for broadcasts and other Pro features.
Let’s do this, step by step.
Step 01
Check tools and available events
Open Setup → Tools → Plugins → E-Commerce → FunnelKit Automations. Enable the required tools, Save changes and reconnect. Discover list-events and list-actions.
Check which events can start an automation and which actions are available. Use test contacts you control for this walkthrough.
Step 02
Create an inactive automation
Review the plan, then create-automation. Read it with get-automation before configuring its event through update-automation.
Create the automation with a clear name. It starts off. Set its starting event only after reviewing the returned settings.
Propose a simple FunnelKit automation using available events and actions. Keep it inactive. Use only test contacts, dry-run supported changes, and do not send or schedule anything.
Step 03
Add and inspect the steps
Add the intended wait, action or conditional steps and update their data and flow. Open the native editor to inspect the complete path.
Add one step at a time. Check the wait and both branches of any condition. Keep the automation off while reviewing it.
Step 04
Prepare a broadcast draft when available
With Automations Pro, create-broadcast as a draft. Update details, audience, and content/sender in steps 1, 2 and 3. Run send-broadcast with dry_run to inspect recipient count.
Review the sender, message and audience. Preview how many people would receive it. A dry run checks the request without sending the broadcast.
Step 05
Review before activation or sending
Only with the site owner’s approval, activate the reviewed test automation or confirm an intended send/schedule. Tag/list assignments can trigger active automations; review those too.
Turning an automation on or assigning a contact’s tag can start real actions. Pause for a clear decision before doing either. Sending and scheduling need explicit confirmation; a draft alone is not permission to send.
Step 06
Check the result and recovery limits
Inspect the native status and History. Switching an automation off does not recall sent messages. Read reasons for non-undoable entries, including sends, schedules and contact deletions.
Check the actual result after an approved action. History cannot recall messages already sent. Keep the demonstration limited to your test contacts and review every action’s recovery limits.
You’re done when…
The automation and broadcast are reviewed drafts unless activation or sending was explicitly approved.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.