Question 1

What can trigger an automation?

Accepted Answer

Four types: (1) Events — any state change inside PrimeBase, such as an invoice becoming overdue, a customer status changing, a task being marked complete, or a GRN being confirmed. (2) Schedules — run at a fixed time, on a recurring interval, or via a custom CRON expression. (3) Webhooks — receive a POST request from any external system (Stripe, Shopify, your own apps). (4) Manual — trigger on demand from any record or run bulk against a filtered list.

Question 2

What actions can an automation take?

Accepted Answer

Send an email (using a template with field variables), create a task, update a field on any record, change a status, add or remove a tag, assign a user, send an outbound webhook, create a new record in any module, or send a notification. Actions can be chained across different modules in the same automation — for example, create a task in CRM and post a webhook to Slack in the same run.

Question 3

How does conditional branching work?

Accepted Answer

Insert a Condition step and define an IF rule using any field from the trigger record. If the condition is true, the Yes branch executes; otherwise the No (or ELSE IF) branch runs. Branches are independent multi-step sequences — each can have its own actions, delays, and even nested conditions. You can have multiple ELSE IF branches before a final ELSE.

Question 4

What is dry-run mode and how do I use it?

Accepted Answer

Dry-run mode simulates the automation against real data without executing any side effects. Emails are not sent, tasks are not created, records are not modified. After the dry run, you see exactly which records matched the trigger, which branch each record would have taken, and what each action would have done. Switch to Live when you're confident the logic is correct.

Question 5

How do I see what an automation did?

Accepted Answer

Every execution is logged in the Execution History. You can see each run: when it fired, what triggered it, how many records were processed, and whether it succeeded. Click into any run to see step-level detail — which step ran, what the input and output were, how long it took, and any error messages if a step failed. History is retained indefinitely.

Question 6

Can automations loop over multiple records at once?

Accepted Answer

Yes. Use a Loop step to iterate over a filtered list of records — for example, "for each overdue invoice in this customer's account, send a reminder." The loop body runs once per record, with that record's fields available as variables. You can also trigger an automation manually against a bulk selection of records from any list view.

Question 7

What is workflow automation software?

Accepted Answer

Workflow automation software lets you trigger sequences of actions automatically — when an event happens, on a schedule, or in response to an external system. PrimeBase workflow automation runs across every module: send an email when an invoice is overdue, create a task when a deal is won, fire a webhook when a form is submitted. No code required.

Question 8

Does PrimeBase automation replace Zapier?

Accepted Answer

For most internal automations, yes. PrimeBase automations run inside the platform — every field, every record, every status is available as a trigger or action without webhook mapping. Zapier still wins for connecting PrimeBase to outside tools (Slack notifications, Google Sheets exports, third-party APIs) — and PrimeBase supports inbound and outbound webhooks for those cases. Internal-to-PrimeBase workflows: use PrimeBase. PrimeBase-to-external: use webhooks or Zapier.

Question 9

Will my automations break when I update a field?

Accepted Answer

No. PrimeBase automations reference fields by ID, not by label. Renaming a field in your CRM doesn't break the automation. Adding a new pipeline stage doesn't either. The dry-run mode lets you test against real data before any automation goes live, and the step-level execution history shows you exactly what happened on every run.

Build it once. It runs forever.

You know exactly what should happen next. You just have to remember to do it.

The automation engine built into your data.

Visual multi-step builder. With branching.

Event, schedule, webhook, or manual. You pick.

Conditional branching. Different paths for different cases.

Actions across every module.

Delays, waits, and loops.

Dry-run mode. Test without side effects.

Every module. Every event.

Full execution history. Every run, logged.

Step-level audit. Know exactly what happened.

Automation is the connective tissue. Every module is a trigger. Every module is an action.

What people ask before they switch.

Stop doing it manually. Start doing it once.