BranchIS Make integrationAutomate BranchIS with Make.
Can Make keep your BranchIS projects and tasks moving without copy and paste? The BranchIS Make integration gives you 17 modules: 3 triggers, 11 actions and 3 searches. This guide helps ops leads connect the account and build a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the BranchIS Make integration do for you?
The BranchIS Make integration links your BranchIS account to Make, a no-code tool where you build a scenario (the automation itself, a chain of small bricks called modules). Make watches your projects and tasks, then creates, updates or looks them up for you, so the busywork between tools stops landing on your desk.
Kick off new work without retyping it. Start with Watch Projects, then let Create a Task add the first to-do inside BranchIS. Nobody has to remember the setup checklist anymore.
Tell people when something moves. Pair Watch Tasks with Send chat message so a change in a task reaches the right conversation. If you want the full record in the message, add Get Task Detail in between.
Keep links and records in one place. When a form tool or a CRM produces a document, Search Projects finds the matching project and Attach an URL link to the project pins it there. Tools like the 123FormBuilder Make integration can feed that flow.
One honest caveat: Make's own documentation for BranchIS is limited, because little public information exists about the app. The module names are clear, but field details are not written down, so open each module and read what Make lists. The Make review covers how the editor behaves in general. If you are also weighing n8n, the n8n vs Make comparison lays out the criteria side by side.
How do you connect BranchIS to Make?
- 01
Add a BranchIS module
In a new scenario, click the +, type BranchIS and pick any module. Then click Create a connection. A connection is your BranchIS account linked to Make once, and every BranchIS module reuses it.
- 02
Name it and authorize Make
Give the connection a name if you like, handy when you run several BranchIS accounts. Then follow the window that opens: either you authorize Make on the BranchIS page, or you paste the key BranchIS gives you.
- 03
Save and check the lists
Click Save. Back in the module, Make now lists what it can read from your account. If those lists fill up, the connection works. You can move on to the fields.
Build your first scenario with BranchIS
GoalWhen a new project shows up in BranchIS, Make adds a first task to it.
- 01
Create the scenario
Open the Scenarios page in Make, create a new scenario and click the + in the middle of the empty canvas to place your first module.
- 02
Place Watch Projects
Search BranchIS, choose Watch Projects and pick your connection. This scheduled trigger has a clock badge: Make checks BranchIS on the scenario's schedule.
- 03
Add Create a Task
Click the + on the right of the trigger, pick Create a Task and map the project coming from the first module, so the task lands in the right place.
- 04
Test with Run once
Click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one project. Check that the task appeared in BranchIS.
- 05
Schedule and switch on
Open Scheduling on the first module. A new scenario runs every 15 minutes by default, and the Free plan allows 15 minutes at the shortest. Then switch the scenario on.
BranchIS triggers: what starts a scenario
3 modules start a scenario when something happens in BranchIS. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by BranchIS as soon as it happens.
Watch Project Formation Events
triggerIn the docs onlyThis trigger gives you a scenario that reacts to the formation events of your BranchIS projects, which by its name means the stage where a project takes shape. The documentation does not describe which events count, so run it once to see what arrives.
Watch Projects
triggerIn the docs onlyYour scenario starts from the projects in BranchIS, one bundle per project Make picks up, which makes it the natural first module for any onboarding flow built around a project.
Watch Tasks
triggerIn the docs onlyHere the unit is the task: every task Make finds becomes a bundle, so a single task change can drive a message, an update elsewhere or a lookup.
BranchIS modules: actions and searches
BranchIS gives you 14 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Attach an URL link to the project
ActionIn the docs onlyYou get a web link pinned to a BranchIS project, so a contract, a shared folder or a proposal sits where the team already looks.
Attach an URL link to the task
ActionIn the docs onlySame idea one level down: the link goes on a single task, which suits a brief, a ticket or a file tied to one piece of work rather than the whole project.
Create a Project
ActionIn the docs onlyA new project appears in BranchIS without anyone opening the app, built from data that arrives in the scenario from a form, a CRM deal or a signed quote.
Create a Task
ActionIn the docs onlyThis module adds a to-do to BranchIS for you, which is the quickest way to turn an event in another tool into work someone will actually see and pick up.
Get Project Detail
ActionIn the docs onlyHand it one project and, as its name says, you get back its details, useful when a later module needs more than what the trigger or search passed on.
Get Task Detail
ActionIn the docs onlyThe task counterpart: from one task reference, Make pulls the complete task, so you can put its content into a message or copy it to another tool.
Make an API Call
ActionIn the docs onlyWhen none of the listed modules does what you need, this one lets you call any endpoint of the BranchIS API from your scenario, reusing the same connection.
Search Projects
SearchIn the docs onlyYou look up projects in BranchIS and get back zero, one or several results, each as its own bundle, which the next modules then handle one by one.
Search Tasks
SearchIn the docs onlyThe search for work items: it returns the BranchIS tasks that match, possibly none, possibly many, and each one flows on separately through the scenario.
Search Timers
SearchIn the docs onlyThis search brings back the timers recorded in BranchIS, the time tracking side of your work, so you can send that data somewhere else without exporting it by hand.
Send chat message
ActionIn the docs onlyGoing by its name, your scenario can post a message in the BranchIS chat, which keeps people informed inside the tool they already use instead of adding another notification channel.
Show Plan
ActionIn the docs onlyGoing by its name, this module returns plan information from BranchIS. The documentation gives no description, so add it on its own and click Run once to see what it returns in your account.
Update a Project
ActionIn the docs onlyYou change an existing BranchIS project from the scenario, so the project stays in sync with what happens in your CRM or your billing tool.
Update a Task
ActionIn the docs onlyThis one edits a task that already exists, which saves someone from reopening BranchIS to tick a box or change a detail after the work happened elsewhere.
Need help automating BranchIS with Make?
A person reads every message.
