← Back to all guides
Automate · Automation · ~10 min read

Activepieces

Coming soon

Build no-code automations between your tools: triggers, actions, branching - and get the repetitive work off your plate.

See Activepieces in the tool catalogue →
Coming soon. This tool isn't switched on for your company yet - but you can read up in advance. The guide reflects how it will work on your Brundo instance.

What is Activepieces?

Activepieces connects your tools and automates the repetitive work between them: "when X happens in one tool, do Y in another." New form response → create CRM contact. New signed contract → message the team channel. It replaces Zapier or Make - without per-task pricing that punishes success.

How it works: you build flows. Every flow starts with a trigger (the event that starts it) followed by actions (what happens), optionally with branches and conditions. Connectors - called pieces - cover common apps, including much of your Brundo stack; webhooks and code steps cover the rest.

Getting started

  1. Log in at your company's Activepieces address with your Brundo account.
  2. Connect your tools first. Before building anything, set up Connections - the stored logins Activepieces uses to act in your other tools. For each tool you plan to automate: Google/Gmail means signing in and granting access; Mattermost needs your instance URL and a bot token or webhook; AI steps (e.g. OpenAI) need an API key pasted in; and your Brundo tools (Twenty, Formbricks, Plane...) each connect with an API key from their settings. Connections are stored securely, created once, and reused by every flow. You can also add them mid-build when a step prompts you - but doing the main ones upfront makes flow building much smoother.
  3. Create your first flow: + New flow. Pick a trigger - start simple: a Schedule trigger (e.g. every Monday 9:00).
  4. Add an action: e.g. send a Mattermost message ("Weekly reminder: submit timesheets"), using the connection you created in step 2.
  5. Test it: every step has a Test button showing real sample data. Test each step before publishing.
  6. Publish. The flow now runs on its own. Congratulations - you've automated your first chore.

Where do API keys come from? Usually the target tool's settings, under "API" or "Integrations". If you can't find one, ask Brundo - we'll generate the keys for your stack tools and help you add the connections.

Core concepts

Triggers

What starts a flow: a schedule, a webhook, or an event in an app (new form response, new email, new record).

Actions & data mapping

Each action can use data from previous steps - the form respondent's email becomes the CRM contact's email. You map fields by picking from the sample data of earlier steps.

Branches & conditions

"If the deal value is over €10k, also notify the director." Branching keeps one flow handling multiple cases.

Runs & history

Every execution is logged with each step's input and output. When something misbehaves, the run history is where you look.

Recipes for your Brundo stack

Form lead → CRM + team alert

  1. Trigger: Formbricks - new response on your contact form.
  2. Action: Twenty CRM - create person (map name, email, message into fields).
  3. Action: Mattermost - post to the sales channel: "New lead: {name} - {message}".

Signed contract → team notification + task

  1. Trigger: DocuSeal - submission completed (webhook).
  2. Action: Mattermost - announce in the projects channel.
  3. Action: Plane - create an onboarding issue for the new client.

Daily digest

  1. Trigger: Schedule - weekdays 08:30.
  2. Actions: pull yesterday's new CRM leads and open support conversations.
  3. Action: post a short digest to the management channel.

Tips & good habits

  • Automate what you already do manually and understand well - don't automate a process you haven't stabilised.
  • Name flows descriptively: "Formbricks lead → Twenty + Mattermost", future-you will thank you.
  • One flow, one job. Two small flows beat one tangled one.
  • Add a failure notification (Activepieces can alert you when a run errors) so silent breakage doesn't cost you leads.
  • Check run history after any connected app changes - renamed form fields are the classic silent breaker.

Troubleshooting & FAQ

My flow didn't run. Check it's published (not draft), then check the run history for errors, then re-test the trigger. Connection tokens occasionally need refreshing.

The app I need has no piece. If it has an API, the HTTP/webhook steps can talk to it - ask Brundo, this is usually a 30-minute job for us.

Can flows run on a schedule rather than an event? Yes - the Schedule trigger does cron-style timing (hourly, daily, specific days).

Is there a run limit? On your own instance there's no artificial per-task pricing. Extremely high volumes are an infrastructure question - talk to Brundo.

Useful resources

Curated for the version Brundo hosts (community / self-hosted editions) — cloud-only or enterprise-only material is skipped.