How to Create a Pulse - Custom AI Prompts for Your Site

Step-by-step guide to creating, scheduling, and managing Pulses in Blockli Assistant.

Philip Ikpeiwunna

Last Update 2 bulan yang lalu

What is a Pulse?


A Pulse is an automated AI job you configure inside Blockli Assistant. Instead of manually sending prompts to your AI agent, a Pulse does it for you — on a schedule, in response to events on your site, or as a one-off task. Each Pulse targets a specific audience (your members, admins, or a FluentCRM segment) and uses an AI prompt template you write to drive personalised actions.

Navigate to Pulses


Go to Blockli Assistant - Settings - Pulses in your WordPress dashboard.


Step 1 - Choose a Pulse Type
When you click + New Pulse, you will first choose one of three types:
Task - Sends AI-powered messages or actions to a targeted audience on a recurring schedule or as a one-time run. Great for weekly engagement nudges, drip-style outreach, and personalised member check-ins.
Flow - Fires automatically when a WordPress event occurs (a form is submitted, a purchase is made, a user joins a group, and so on). Ideal for real-time AI actions triggered by activity on your site.
Report - Generates a site-wide summary (orders, revenue, new users, engagement) and delivers it to selected administrators on a schedule. No audience selection is needed - the AI queries your site data directly.

Creating a Task Pulse


After choosing Task, fill in the following fields:
1. Pulse Name (required) - A descriptive name for this pulse. Used as the {pulse_name} placeholder in your prompt template.2. Description - Optional. A brief note about what this pulse does.3. Audience (required) - Choose which users receive the pulse. Options: BuddyBoss Groups, WordPress Roles, FluentCRM Lists, FluentCRM Tags, All Users, or Site Admin. After selecting a type, choose the specific groups, roles, lists, or tags. Use Preview Users to see how many users match your criteria before saving.
4. AI Prompt Template (required) - The instruction sent to the AI for each user.
5. AI Tools - Select which tools the AI can use when this pulse runs. Click a category card to expand it and toggle individual tools on or off. Leave empty to use global defaults.
6. Override Agent Status - By default only users with an active agent status receive pulses. Enable this to include all users regardless of status.
7. Trigger Type - Choose Scheduled (recurring) or One-Time.
8. Schedule (for Scheduled) - Set the interval (hourly, daily, weekly, monthly), the time of day, and the day of the week for weekly schedules.
Click Create a Pulse to save.

Creating a Flow Pulse


After choosing Flow, fill in the following:
1. Pulse Name and Description.
2. Triggers (required) - Choose one or more events that will fire this pulse. Triggers are grouped by integration: Form Submissions (Elementor, Contact Form 7, WPForms, Gravity Forms, FluentForms), WooCommerce (new order, order completed/processing/cancelled/failed, order status changed, product created/updated/out of stock, add to cart, customer created, coupon created), WooCommerce Subscriptions (created, renewed, cancelled, expired, trial ended, renewal failed, status changed), WordPress (post published/updated/trashed, user registered/updated/login/logout/deleted, role changed, comment posted), LearnDash (course/lesson/topic completed, quiz completed/passed/failed, course enrolled/unenrolled, assignment uploaded), BuddyBoss / BuddyPress (group joined/left, activity posted/commented, forum topic/reply created, friend request/accepted/rejected, private message sent, profile updated, member type changed, user suspended/unsuspended), FluentCRM (contact created, tag added/removed, list added, status changed), GamiPress (achievement earned, rank earned, points awarded), GiveWP (donation completed, recurring donation), MemberPress (membership purchased, subscription renewed/cancelled/expired, payment failed), Webhook (incoming webhook - a secret URL is auto-generated), Custom WP Hook (listen on any WordPress action hook by name).
3. Multi-trigger logic - When more than one trigger is selected, set the mode to Any (fire when any trigger fires) or All (fire only when all selected triggers have fired). Enable sequential mode to require triggers to fire in a specific order.
4. Audience - Choose which users the AI acts on when the trigger fires (same options as Task).
5. AI Prompt Template (required) - Available placeholders: {user_name}, {user_id}, {site_name}, {pulse_name}, {trigger_event}, {trigger_data}. This is optional. The trigger payload already contains all the data and the agent can resolve this on its own.
6. AI Tools - Same tool picker as Task. Select the categories and individual tools the AI can use when the flow fires.
Click Create a Pulse to save. The flow begins listening for the selected triggers immediately.

Creating a Report Pulse


After choosing Report, fill in:
1. Pulse Name and Description.
2. Select Admins - Choose which administrator accounts receive the report. Leave all unchecked to send to all administrators.
3. AI Prompt Template (required) - Available placeholders: {site_name}, {pulse_name}. Write a prompt that instructs the AI to query site data and present a concise summary.
4. AI Tools - Select the tools the AI can use to gather data (for example WooCommerce tools, LearnDash reporting tools, WordPress user tools).
5. Schedule - Set the recurring interval, time of day, and day of the week.
Click Create a Pulse to save.


Tools and Approvals


The tool picker shows your available integrations as category cards - BuddyBoss, WooCommerce, FluentCRM, LearnDash, Discord, Email, WhatsApp, and more. Click a category to expand it and see individual tools. Toggle individual tools on or off. A badge on the card shows how many tools are currently selected.
Tool approvals - Each selected tool has an approval toggle. Set it to Always require approval to pause the AI and request human sign-off before that tool executes. Configure the notification channel as Email or WhatsApp. Approvals let you keep humans in the loop for sensitive actions like sending messages, updating records, or processing payments.
Infrastructure tools (document extraction, delayed pulse scheduling) are always available to every pulse and do not appear in the tool picker.


Managing Your Pulses


The Pulses list shows all pulses with columns for Name, Type (Task / Flow / Report), Target Audience, Schedule or Trigger, Last Run, Next Run, Status, and Actions.
Triggering manually - Click the play icon next to any pulse to run it immediately. A confirmation dialog appears before it fires.
Rerunning a past run - Open the edit view for a pulse to see its run history. Each past run has a Rerun button. Use this to repeat a failed run or test changes.
Enabling and Disabling - Use the toggle in the Actions column to pause or resume a pulse without deleting it.
Approving or Denying - If a run is waiting for tool approval, the run history shows Approve and Deny buttons. Approve to let the AI proceed with the action, or Deny to cancel it.


Common Use Cases


Weekly member engagement (Task) - Every Monday at 9 am, send a personalised check-in to all members in a BuddyBoss group. The AI reviews each member's recent activity and suggests a next step.
Real-time onboarding (Flow) - Fire when a user completes a LearnDash course. The AI sends a congratulations message via BuddyBoss, awards GamiPress points, and tags the contact in FluentCRM.
New order follow-up (Flow) - Fire on WooCommerce order completed. The AI sends a personalised thank-you, checks upsell eligibility, and creates a FluentCRM tag.
Daily admin briefing (Report) - Every morning, the AI queries WooCommerce revenue, new registrations, and low-stock products, then emails a summary to selected admins.
One-time campaign (Task, One-Time) - Send a targeted AI-written message to a FluentCRM tag segment without setting up a recurring schedule.


Tips


Be specific in your prompt - Tell the AI exactly what to do and what format to use. The more precise the instruction, the more consistent the output.


Use Preview Users - Always preview your audience before saving to confirm the right users are targeted.
Test with a one-time run first - For recurring tasks, create a one-time version to verify the prompt and tools work correctly before switching to a schedule.

Use tool approvals for sensitive actions - Enable approval on tools that send messages, modify records, or process payments to keep humans in the loop.
Check run history - After a pulse fires, open the edit view to see the full run log, including which tools were called and whether any are pending approval.

Was this article helpful?

0 out of 0 liked this article

Still need help? Message Us