Resources · Make integration

SingleCase Make integrationAutomate SingleCase with Make.

Can Make take the busywork out of SingleCase? The SingleCase Make integration gives you 15 modules: 3 triggers that watch cases, changes and due dates, 5 actions and 7 searches. This page shows how to link your account and build a first scenario step by step.

Try the SingleCase integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SingleCase Make integration do for you?

The SingleCase Make integration links your SingleCase account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates or looks something up. Once linked, cases, clients, tasks and reminders can move between SingleCase and your other apps without copy and paste.

New clients filed without retyping. When a request lands in another app, Add Client records the person in SingleCase and Add Case opens the matching case right after, so nobody rekeys the same name twice.

Deadlines that reach the right people. Watch Due Dates starts a scenario when SingleCase has a date coming up, and the next module can pass the details to the tool your team actually reads.

A clean export of what changed. Watch Changes and the List modules, such as List Cases or List Tasks, feed a report or a shared sheet with the latest state of your files.

Know the limits before you start: Make itself says its SingleCase documentation is limited, and the app has no universal API module, so what you can do is exactly the 15 modules below. If you are weighing tools, the n8n vs Make comparison sets out the criteria, and the Make pricing page explains what each plan includes.

Connect

How do you connect SingleCase to Make?

  1. 01

    Add a SingleCase module

    In your scenario, click the +, search for SingleCase and pick any of its modules. Then click Create a connection. A connection is your SingleCase account linked to Make once, and every SingleCase module reuses it.

  2. 02

    Name the connection

    This step is optional, but a clear name such as the office or the account owner helps when several people share the same Make workspace and each one links a different SingleCase login.

  3. 03

    Authorize and save

    Make then asks you to approve access on the SingleCase side, or to paste the key SingleCase gives you. Follow what the window shows, then click Save. The module can now read your SingleCase data.

First scenario

Your first scenario with SingleCase

GoalWhen a new request arrives in another app, Make adds the client in SingleCase and opens a case for them.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where requests reach you first, such as your form tool, so it starts the flow.

  2. 02

    Add Add Client

    Click the + on the right of that first module, search for SingleCase and choose Add Client. Create the connection, then map the name and details from the request into the fields Make shows.

  3. 03

    Chain Add Case

    Add one more SingleCase module, Add Case. Fill its fields with values from the previous modules, so the case is tied to the client that Add Client just created.

  4. 04

    Test with Run once

    Click Run once and send a test request. Each module then shows the bundles it received, a bundle being one item passed along, so you can check that the client and the case look right in SingleCase.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default; keep that or change it, then switch the scenario on so it runs without you.

Triggers

What can start a SingleCase scenario?

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

SingleCase1Watch Cases

Watch Cases

triggerIn the docs only

You get a scenario that starts from the cases in SingleCase, so work that begins with a case can flow straight into your other tools. Make lists this module under SingleCase without an official description, and the name is the best guide to what it returns.

How it fires
scheduled, Make checks SingleCase on the scenario's schedule, shown by the clock badge on the module.
When to use it
a new case should create a folder, a message or a line in a tracker elsewhere.
Watch out
run it once before switching it on and read the bundle, because only that output tells you which case details you can map.
SingleCase2Watch Changes

Watch Changes

triggerIn the docs only

This trigger hands your scenario whatever SingleCase reports as changed, which keeps a report, a sheet or a second tool in step with your files. It is the one to choose when updates matter more than new records.

How it fires
scheduled, Make checks SingleCase at each run of the scenario rather than being alerted by the app.
When to use it
another system must mirror what your team edits in SingleCase.
Watch out
the documentation does not say which kinds of change it covers, so test it with a real edit and look at what arrives.
SingleCase3Watch Due Dates

Watch Due Dates

triggerIn the docs only

With this module, dates in SingleCase turn into a starting point, so an upcoming deadline can reach people who never open the app. Choose it over Watch Cases when the date, not the case itself, is what should set things moving.

How it fires
scheduled, Make looks at SingleCase each time the scenario's clock comes around.
When to use it
a colleague needs a heads-up in the messaging tool the team already reads.
Watch out
because checks follow the schedule, a date added between two runs is only picked up at the next one.
Modules

What else can Make do in SingleCase?

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

SingleCase1

Add Case

ActionIn the docs only

Opens a case in SingleCase from data that lives elsewhere, so a signed request or a form entry becomes a file without anyone typing it in.

When to use it
right after Add Client, or when the client already exists and a new matter comes in.
Watch out
each run creates a case, so test with Run once before activating to avoid duplicates.
SingleCase2

Add Client

ActionIn the docs only

Records a new client in SingleCase straight from the app where the contact first appeared, which saves a manual entry and keeps spellings consistent.

When to use it
as the first SingleCase step when someone new gets in touch.
Watch out
nothing in the documentation says it checks for an existing client, so place List Clients before it if duplicates worry you.
SingleCase3

Get a Message

ActionIn the docs only

Fetches a single message from SingleCase so its content can travel to another tool, for example to be archived or forwarded to someone outside the app.

When to use it
you already know which message you want, typically from an earlier module in the flow.
Watch out
it reads one message; to go through several, List Messages is the better fit.
SingleCase4

Get a Reminder

ActionIn the docs only

Brings back one reminder from SingleCase with its details, ready to be copied into a calendar or a chat message outside the app.

When to use it
a previous module handed you a reminder and you need more than what it carried.
Watch out
the documentation lists no fields, so read the bundle after Run once before mapping anything from it.
SingleCase5

Get a Task

ActionIn the docs only

Pulls the record of one SingleCase task, so the next module can show its details in another tool.

When to use it
after Watch Due Dates or List Tasks, to enrich a notification with the task itself.
Watch out
it needs to know which task to fetch, so it rarely works as the first module of a scenario.
SingleCase6

List Cases

SearchIn the docs only

Returns the cases SingleCase holds, one bundle per case, which is handy to build a report or feed a spreadsheet with your current files.

When to use it
you want a snapshot of every case rather than a reaction to a single new one.
Watch out
each returned case can trigger the next modules once, and every module run counts as an operation on your plan.
SingleCase7

List Clients

SearchIn the docs only

Gives you the clients stored in SingleCase, so a scenario can check who is already there before adding anyone or sync the list to a CRM.

When to use it
just before Add Client, to avoid creating the same person twice.
Watch out
a search can return zero results, so plan what the scenario should do when nobody matches.
SingleCase8

List Countries

SearchIn the docs only

Returns the countries SingleCase knows, which helps when another app sends a country name that has to match what SingleCase expects.

When to use it
while building an Add Client flow for contacts from several countries.
Watch out
it is a reference list, not a business record, so it seldom belongs at the heart of a scenario.
SingleCase9

List Messages

SearchIn the docs only

Collects the messages in SingleCase as separate bundles, a practical way to archive exchanges or pass them to a shared inbox.

When to use it
you need a batch of messages rather than the single one Get a Message returns.
Watch out
a long list means many bundles, and each one run through later modules costs operations.
SingleCase10

List Reminders

SearchIn the docs only

Lists the reminders set in SingleCase so you can push them into a shared calendar or a team digest in one pass.

When to use it
you want every reminder at once, while Watch Due Dates suits reacting to dates as they come.
Watch out
the documentation gives no filter details, so check after Run once whether the output needs sorting.
SingleCase11

List Tasks

SearchIn the docs only

Brings back the tasks recorded in SingleCase, useful to share workloads with a project tool or to spot open work in a report.

When to use it
a manager wants the task list outside SingleCase without logging in.
Watch out
pair it with Get a Task only when the list lacks a detail you need, otherwise it doubles the operations.
SingleCase12

List Users

SearchIn the docs only

Returns the people who have access to SingleCase, which lets a scenario match an owner name from another app to a real user.

When to use it
assigning cases or tasks based on data arriving from outside the app.
Watch out
user lists change as the team does, so look them up in the flow instead of hard-coding a name.
Need help

Need help automating SingleCase with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the SingleCase Make integration free?
Yes, SingleCase is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans, Core, Pro, Teams and Enterprise, bring the interval down to 1 minute and allow unlimited active scenarios. Usage is counted in operations, one per module run on one bundle. Your SingleCase subscription is a separate matter.
02What do you need to connect SingleCase to Make?
A SingleCase account and a Make account. The Make documentation lists no prerequisites and no official connection steps for SingleCase, so you follow the generic path: add a SingleCase module, click Create a connection, optionally name it, approve access on the SingleCase side or paste the key it gives you, then click Save. The connection is stored once and every SingleCase module in your scenarios reuses it, so this is done only once per account.
03Do SingleCase triggers start a scenario instantly?
No, as far as their names tell. The 3 SingleCase triggers, Watch Cases, Watch Changes and Watch Due Dates, work as scheduled triggers: Make checks SingleCase on the scenario's schedule. The documentation gives no type, so look for the clock badge on the module to confirm. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute between checks. If speed matters, set the shortest interval your plan allows on the first module.
04What if a SingleCase module you need is missing?
SingleCase has no Make an API Call module in Make, so you cannot reach features beyond the 15 listed modules from inside the app. Make also states its SingleCase documentation is limited because little public information exists. Start by combining the existing modules, a List search followed by a Get module often covers the need. If it still falls short, another app in your stack may hold the data, or the team at Hack'celeration can help study the case.
05Make or n8n for SingleCase?
It depends on the criteria that matter to your team. On the Make side, SingleCase comes with 15 modules, 3 of them scheduled triggers, and works from the Free plan. Before choosing, check whether n8n offers a SingleCase node and which operations it covers, then compare the two on the modules you really need. The n8n vs Make comparison linked earlier on this page walks through the criteria without ranking either tool.
Same platform

Other docs you might need on this stack.

Browse all integrations