Skip to main content

Step 4: Setting Up Your First Playbook

B
Written by BonData Support
Updated over a month ago

What Are Playbooks?

Playbooks in BonData are automated workflows that let you take action on data across your connected systems. Each Playbook defines:

  • Conditions – when something should happen (e.g., "Accounts missing owner")

  • Actions – what should happen (e.g., "Send Slack notification", "Update record in Salesforce")

BonData constantly monitors your systems and executes your playbooks when your defined rules are met—no code required.


Why Use Playbooks?

  • Automate Repetitive Tasks – Save time on manual exports, updates, and alerts.

  • Unify Disconnected Systems – Sync records, trigger actions, and gain visibility across CRMs, support tools, billing platforms, and more.

  • Stay in Control – Choose whether tasks run automatically or require approval before executing.


Types of Playbooks

  • Automation Playbook – Triggers actions based on conditions like missing values or risk signals.

  • Migration Playbook – Moves data between systems without storing it in BonData, with explicit field mapping.


Quick Start: Building Your First Playbook

  1. Access the Playbook Builder
    Go to the BonData dashboard → My PlaybooksCreate New Playbook

  2. Name & Describe
    Give it a clear name (e.g., “Accounts Missing Owner”) and optional description.

  3. Define Conditions (Filters)
    Choose the fields and systems to monitor. You can combine filters using AND/OR logic.

  4. Set Actions
    Decide what to do when filters are matched:

    • Create or update records

    • Send Slack/email alerts

    • Generate CSV

    • Send HTTP request

  5. Choose Execution Mode

    • Automatic: Runs tasks (actions) immediately

    • Manual: Requires your approval for each task

  6. Preview Your Playbook (Dry Run)
    Before running it live, click the "Test" button (top right, next to Run and Save). This creates a preview of the tasks without performing actions—ideal for reviewing what data would be created or updated. Tasks will be shown in the panel on the right hand side of the screen.

  7. Make It Live
    To turn your playbook into a running, automated workflow:

    • Toggle Active (top left)

    • At the bottom of the page, toggle "Do it automatically" (or leave off for manual mode)

    • Click the ⚙️ Gear iconPlaybook Configurations

      • Set trigger type:

        • Always (run every time)

        • On change (run only on new or updated records)

      • Define the run frequency (e.g., every 15 mins or custom cron expression)

    • Click Run to activate the playbook for the first time


Monitoring & Managing Playbooks

  • See Task Previews: Right menu on the Playbook page shows upcoming tasks

  • Track Task Execution:

    • ⚙️ Gear icon next to SaveShow Generated Tasks

    • Monitor task statuses: Running, Pending, Failed, Success


Mentions & Field Mapping

Use "Mentions" to dynamically insert field values from one system into another (e.g., take “Region” from a CSV and insert it into Salesforce's BillingState).

You can also use:

  • Conditional Mentions – Apply logic (e.g., if 1 → “{variable from Region field}”, else → Static value: "Other")

  • Default Values – Use fallback (default) values when source fields are blank


Trigger Behavior Options

  • Change (default) – Only run on newly changed/created records

  • Always – Run every time for all matching records


Use Cases

  • Data Cleanup – Flag or export incomplete records

  • Data Sync – Keep status fields aligned across tools

  • Alerts – Notify teams when rules are met, or periodically with updated information

  • Migrations – Move records from a legacy system into a new platform with field mapping


Best Practices

  • Start small: test with a simple condition and action.

  • Use Test (Dry Run) to validate before activating.

  • Periodically audit filters and field mappings.

  • Monitor task volumes to catch overly broad rules.


FAQs

Can I add multiple actions?
Yes. One playbook can perform several actions per matched record.

Can I test without making changes?
Yes. Use Test or set execution to Manual.

Can I work across systems?
Absolutely. Playbooks can reference multiple integrations.

Can I undo a mistake?
Check the Task Logs for affected records. Since BonData doesn’t store full datasets, rollback is manual in the original systems.

Did this answer your question?