Resources · Make integration

Focuster Make integrationAutomate Focuster with Make.

Can your Focuster to-do list react on its own when work gets done? The Focuster Make integration gives you 5 modules: 2 triggers, 2 actions and 1 search. This guide shows how to link your account and build a first working scenario, step by step.

Try the Focuster integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Focuster Make integration do for you?

The Focuster Make integration links your Focuster account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single step. Make can spot new or completed actions in Focuster, add actions, flip their status and read the pending ones, so tasks move between your apps without copy and paste.

A follow-up that writes itself. A sales rep ticks off a client call in Focuster. New completed action notices it, and Add Action drops the next step into the list, so nothing waits on memory.

Tasks born from other tools. A support ticket, a form reply or a signed quote in another app can end in Add Action, so the request shows up as a Focuster action instead of an email to forward. The reverse works too: New action added can pass each fresh task to a team chat or a shared sheet.

Status kept in sync. When a job is closed elsewhere, Get Actions finds the matching pending action and Toggle action marks it done.

What Make does not offer here: there is no instant trigger and no universal API call module for Focuster, so everything runs on the scenario's schedule and stays within these 5 modules. If you are weighing tools, read our n8n vs Make comparison; to learn the editor properly, the Make training starts from zero, and Make troubleshooting helps when a run fails.

Connect

How do you connect Focuster to Make?

  1. 01

    Copy your API key from Focuster

    You need an active Focuster account. Open the Settings page, scroll down to the Integration section and copy the API key shown there. Keep it at hand for the next step.

  2. 02

    Add a Focuster module in Make

    In your scenario, add any Focuster module and click Create a connection. A connection is your Focuster account linked to Make once, then reused by every Focuster module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several people share the workspace. Paste the API key, or follow the on-screen instructions, and save.

First scenario

Your first scenario with Focuster

GoalWhen an action is completed in Focuster, Make adds the follow-up action to your list.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + to place the first module on the canvas.

  2. 02

    Pick the trigger

    Search for Focuster, choose New completed action and select the connection you created. This module starts the scenario each time it finds an action you have ticked off.

  3. 03

    Add the follow-up

    Click the + on the right of the trigger and pick Add Action. Map data from the completed action into the new one, so the follow-up names the task it comes from.

  4. 04

    Test with Run once

    Complete a test action in Focuster, then click Run once. Open the bubbles above each module to read the bundles, the items passed from one module to the next.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as an operation on your Make plan.

Triggers

Focuster triggers in Make

2 modules start a scenario when something happens in Focuster. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Focuster as soon as it happens.

Focuster1New action added

New action added

Scheduled trigger

In Make“Triggers whenever a new action has been added to any list”

This trigger hands every freshly created Focuster action to the rest of your scenario, whichever list it was added to. You get one bundle per new task, ready to copy into a chat message, a spreadsheet row or another planning tool.

How it fires
scheduled. Make checks Focuster on the scenario's schedule, so a new action appears at the next check rather than the moment you type it.
When to use it
a manager wants the team channel to hear about each task added to Focuster without opening the app.
Watch out
it watches all lists, so filter in the scenario if only one list matters.
Focuster2New completed action

New completed action

Scheduled trigger

In Make“Triggers when a new completed action is found”

With this trigger, finishing a task in Focuster becomes the start of something else. Make picks up each action newly marked as done and passes it on as a bundle, which suits reporting, billing or a follow-up task.

How it fires
scheduled. Make queries Focuster at the interval set on the scenario, not at the second you tick the box.
When to use it
a consultant closes a deliverable and wants a line logged in the client tracker.
Watch out
it only picks up actions completed since its last check, so tick a test action before you click Run once.
Modules

What Focuster can do in Make

Focuster gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Focuster1

Add Action

Action

In Make“Adds a new action to focuster”

Add Action puts a new task in Focuster from data flowing through your scenario, so requests that land in email, forms or a CRM end up in your planning without retyping.

When to use it
a form reply or a signed deal elsewhere should become a to-do the moment the scenario runs.
Watch out
map a clear title from the previous module, or you get vague tasks nobody recognizes.
Focuster2

Toggle action

Action

In Make“Toggles an action completion”

Toggle action flips the completion state of one Focuster action, which lets another app close a task for you once the real work is recorded there.

When to use it
a ticket is marked resolved in your help desk and the matching Focuster task should be ticked off too.
Watch out
as its name says, it flips the state, so on an action that is already done it would likely reopen it. Check the state first.
Focuster3

Get Actions

Search

In Make“Gets pending focuster actions”

Get Actions reads your pending Focuster actions and returns them to the scenario, one bundle each, so later modules can sort, count or send them somewhere.

When to use it
you need to find the open task that matches a closed ticket before Toggle action can act on it.
Watch out
a search can return zero, one or many bundles, so the next module runs once per action found.
Need help

Need help automating Focuster with Make?

A person reads every message.

FAQ

Focuster and Make: common questions

01Is the Focuster Make integration free?
Yes, on the Make side. Focuster is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, and each run can last up to 5 minutes. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run. You still need your own active Focuster account, which has its own pricing set by Focuster.
02What do you need to connect Focuster to Make?
An active Focuster account and its API key. In Focuster, open Settings, scroll to the Integration section and copy the key. In Make, add any Focuster module, click Create a connection, optionally give the connection a name, then paste the key. That single connection is reused by all Focuster modules in every scenario you build afterwards, so you only do it once per account. The connection name is optional, but a clear one helps you spot the right account later, especially when several people share the workspace.
03Does the Focuster trigger fire instantly in Make?
No. Both Focuster triggers, New action added and New completed action, are scheduled: Make checks Focuster on the scenario's schedule rather than being called by Focuster. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans can go down to 1 minute. Plan your scenarios around that delay, for example for follow-ups or logging rather than urgent alerts.
04What if a Focuster module is missing in Make?
It depends on what you need. The Focuster app in Make has 5 modules and no universal API call module, so you cannot reach other parts of Focuster from here. Often the fix is to change the angle: start the scenario from another app and finish it with Add Action or Toggle action. If the need goes beyond these modules, our team can look at your case and suggest another route.
05Should you use Make or n8n for Focuster?
It depends on the tool your team already runs. On Make, Focuster offers 2 scheduled triggers, 2 actions and 1 search, usable from the Free plan with a visual editor and a Run once test. Before switching tools for this app alone, check whether n8n offers a Focuster node that covers the same tasks. The comparison on this site walks through the general differences between both platforms. Pick the platform where your other scenarios already live, so you maintain one set of connections.
Same platform

Other docs you might need on this stack.

Browse all integrations