Actionist·Botstar
B

Botstar

· #377 most-used

Automate chatbot subscriber management and campaign enrolments without code

MarketingCommunicationSupportAIAutomationLead Generation

Botstar is a visual chatbot builder that lets you create and deploy conversational bots for your website and Facebook Messenger without writing code. Its drag-and-drop flow editor, user attribute system, campaign sequences, and checkpoint lead-capture make it a capable front-line engagement layer. Connect it to Actionist and your agents can subscribe and unsubscribe contacts, send targeted messages, manage campaign enrolments, update user attributes, and pull checkpoint records — keeping your chatbot audience in sync with your CRM, support desk, and operations stack without anyone manually updating Botstar.

Try Botstar with ActionistVisit Botstar
Average time saved
7 hours
per person · per month
≈ 1 workdays back

Eliminates manual work. Agents eliminate the manual cycle of reading chatbot checkpoint records, editing campaign rosters, managing subscriber lists, and extracting data into spreadsheets that would otherwise require daily Botstar dashboard visits.

Schedule

What your Botstar agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
Tue–Thu
Tue
Wed
Thu
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

Botstar × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
6Apps spanned
~11 hrsSaved / week
6Personas served
For sales
Featured4 apps

Chatbot lead lands in CRM before the rep checks their inbox

When a visitor completes the lead-gen chatbot and a new row is logged in Google Sheets, the agent reads the Botstar checkpoint record, applies the correct interest tag to the subscriber, creates a fully attributed HubSpot contact, and posts a summary to #sales. The rep sees a qualified lead with chatbot context before they would have even opened Botstar.

~4 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a new lead row is added to the lead-capture Google Sheet
Trigger
Step 1
Google Sheets
Detect new row in lead-capture spreadsheet
read
Step 2
B
Botstar
Get Checkpoint Records for matching Botstar subscriber
write
Step 3
B
Botstar
Add Tag to User based on stated product interest
write
Step 4
HubSpot
Create contact with chatbot attributes pre-filled
write
Step 5
Slack
Post new lead summary to #sales channel
Result
Add Tag to User based on stated product interestCreate contact with chatbot attributes pre-filledPost new lead summary to #sales channel
The win
Saved per run
8 min
Runs / week
~30×
Every chatbot lead reaches the CRM with full context in under a minute
Driven bySales Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    40 min / week
    Manual chatbot lead extraction

    Reps log into Botstar, find checkpoint records, copy lead details, and create CRM contacts by hand — 8 minutes per lead, every day.

    Sales Agent
    0 min
    Agent syncs chatbot leads to CRM automatically

    When a visitor completes the Botstar lead-gen flow, the agent reads the checkpoint record and creates a HubSpot contact within about a minute — no rep has to open Botstar.

  • Marketing
    25 min / week
    Manual Botstar campaign roster management

    The marketing team manually removes contacts from one Botstar campaign and adds them to another whenever a lifecycle stage changes in the CRM.

    Marketing Agent
    0 min
    Agent manages campaign enrolments across systems

    When a contact's lifecycle stage changes in HubSpot, the agent moves them between Botstar campaigns instantly — no manual roster edits.

  • Customer Support
    30 min / week
    Manual chatbot-to-ticket transcription

    Support agents read through Botstar chat transcripts or checkpoint records and manually re-enter the details into the ticketing system for each enquiry.

    Customer Support Agent
    0 min
    Agent creates support tickets from checkpoint records

    Support checkpoint records from the chatbot are automatically converted to structured Zendesk tickets, with issue category and account details pre-filled from the checkpoint data.

  • Human Resources
    20 min / week
    Manual Botstar subscriber management for employees

    HR manually subscribes each new employee to internal bots, sets their attributes, and then manually unsubscribes them when they leave the company.

    Human Resources Agent
    0 min
    Agent enrols and offboards employees from chatbot automatically

    When a new joiner is added to the HRIS, the agent subscribes them to the onboarding bot and sets their role attributes. Leavers are unsubscribed the same day they offboard.

  • Finance
    35 min / week
    Manual billing enquiry extraction from chatbot

    Finance team members log into Botstar, search for billing-related checkpoint records, and manually copy the data into the reconciliation spreadsheet each week.

    Finance Agent
    0 min
    Agent extracts billing enquiries from chatbot checkpoints

    Billing-related checkpoint records from the support chatbot are automatically formatted and appended to the reconciliation sheet — no finance team member needs to touch Botstar.

  • Operations
    25 min / week
    Manual multi-bot subscriber reporting

    An operations analyst logs into Botstar, navigates to each bot, copies the subscriber count, and manually builds a comparison table in a spreadsheet every week.

    Operations Agent
    0 min
    Agent produces cross-bot audience report on schedule

    Every Monday, the agent retrieves subscriber counts for all Botstar bots, calculates week-over-week change, and posts the report to Google Sheets and Slack without anyone opening the Botstar dashboard.

  • Legal
    15 min / week
    Manual opt-out processing in Botstar

    The legal team manually looks up each opt-out request in Botstar, unsubscribes the user from every relevant bot, and records the action in the compliance register one by one.

    Legal Agent
    0 min
    Agent actions opt-outs in Botstar within about a minute

    When an opt-out request is logged in the compliance sheet, the agent unsubscribes the user from all Botstar bots and records the action in the GDPR register without legal team involvement.

+ 100s of other Botstar automations
Average time saved
19 hrs / person / month
Calculator

Calculate what your team saves

Team size
5 people
Hourly rate
$75 / hr
Hours saved / week
9
Hours saved / year
450
Annual ROI
$33,750

Based on Botstar's typical team usage — the visible tasks plus a few other automations the agent runs: ~1.8 hrs / person / week of admin work automated.

Connect

How to plug Botstar into Actionist

Pick the connection method that suits your environment.

Connect Botstar using your account API Access Token. This gives agents access to all bots on your account for subscriber management, messaging, campaign enrolments, attribute updates, and checkpoint reads.

1
Open Botstar Account Settings

Log in to your Botstar account and navigate to Account Settings. Find the API Access Token section.

2
Copy your API token

Copy your API Access Token. If you have not generated one yet, click Generate to create it. Treat the token like a password.

3
Paste into Actionist and test

Paste the token into the API Access Token field below and click Test connection. Actionist runs a read-only bot-list call to verify the handshake.

Credentials you'll need
API Access Token*
Log in to Botstar, go to Account Settings, and copy your API Access Token.
Actions

14 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

0 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

This app has no triggers yet.
FAQs

Questions about Botstar + Actionist

How does Actionist connect to Botstar?
Go to the Apps tab, find Botstar, and click Connect. Botstar authenticates via an API Access Token. Log in to your Botstar account, navigate to Settings, and locate the API Access Token section. Generate or copy your token, then paste it into the API token field in Actionist. Actionist runs a read-only test call against your bot list to confirm the connection before any agents begin work.
What Botstar permissions does my API token need?
Your Botstar API Access Token inherits the permissions of the Botstar account that generated it. To allow agents to read subscriber data and analytics, the token needs read access. To send messages, add or remove subscribers from campaigns, update user attributes, or create checkpoints, the account must have editor-level access to the bots you want agents to work with. If you manage multiple bots, the token gives access to all bots associated with that account.
Can agents combine Botstar with other tools in the same task?
Yes. Botstar is designed to work alongside your existing stack. Common pairings include: routing new Botstar subscribers into HubSpot or a CRM when they complete a chatbot flow; sending a Slack notification when a subscriber is added to a high-intent campaign; logging Botstar checkpoint data into Google Sheets for reporting; and triggering follow-up actions in other apps when a user's attribute is updated. Any of Actionist's connected apps can send or receive data alongside Botstar in the same agent task.
What are the most common things agents do with Botstar?
The four patterns that come up most often: (1) lead capture sync — when a visitor completes a Botstar lead-gen flow and a checkpoint is saved, the agent immediately pushes that contact into your CRM; (2) campaign enrolment — subscribing or unsubscribing users from Botstar drip campaigns based on actions they take in other systems; (3) attribute-driven personalisation — updating Botstar user attributes from CRM or order data so the next chatbot message reflects their latest status; (4) subscriber reporting — pulling subscriber counts by bot on a schedule and writing summaries to a Google Sheet for the weekly marketing review.
Does Actionist support both Botstar's Messenger and website chatbot channels?
Botstar supports both Facebook Messenger and website chatbots from a single dashboard. The API actions available through Actionist work across bots regardless of channel — so you can subscribe a user, send them a message, tag them, or update their attributes whether they interacted on Messenger or your website widget. When you specify an action you reference the bot ID and the user's chat ID, not the channel.
How do Subscribe and Unsubscribe work inside an agent task?
Botstar's Subscribe action adds a user to a bot's subscriber list even if they previously unsubscribed, while Unsubscribe removes them so they no longer receive broadcast or campaign messages. Agents use these in concert with your CRM: if a contact's status changes to 'churned' in HubSpot, the agent calls Unsubscribe in Botstar within about a minute; if a lead is re-engaged, it calls Subscribe again. This keeps your chatbot audience in sync with your customer lifecycle without any manual list management.
How does Actionist work with Botstar checkpoints?
Botstar's checkpoint feature captures structured data from a chatbot session — lead details, orders, support inquiries — into a checkpoint record. When an agent reads this checkpoint data, it can route the information to any downstream system: writing a new contact to your CRM, creating a support ticket, logging an order to Google Sheets, or posting a Slack notification. The Save to Checkpoint action can also be triggered externally, letting an agent write data back into Botstar that the next chatbot interaction can reference.
Can agents react to Botstar events in real time?
Botstar does not expose a native webhook trigger that Actionist can subscribe to directly. Agent tasks for Botstar are best structured as scheduled checks — for example, polling for new checkpoint records or updated subscriber counts on a cadence — or as reactions to events in other connected apps (a new CRM entry, a Slack message, a form submission) that then take action in Botstar. This is a Botstar platform-level characteristic, not an Actionist limitation.