Resources · Make integration

Smartcat Make integrationAutomate Smartcat with Make.

What happens in your other tools when a Smartcat project is finished? The Smartcat Make integration gives you 5 modules: 1 trigger that spots completed projects, 3 actions and 1 search. This guide shows localization and ops teams how to connect the account and build a first scenario.

Try the Smartcat integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Smartcat Make integration do for you?

The Smartcat Make integration links your Smartcat company account to Make, a visual tool where you build a scenario (the automation itself, a chain of bricks called modules). Make can notice when a translation project is completed, read or list your projects, and remove the ones you no longer need, all without writing code.

A cleaner project list. Pair Watch Completed Project with Delete a Project and every finished job leaves your workspace once it is done, so project managers only see the work still in progress.

A handoff that starts on its own. When the trigger picks up a completed project, Get a Project reads its details, and the next module in the scenario can pass them to the tool where your sales or support team works. Each item that travels between modules is called a bundle: here, one project.

An inventory on demand. List Projects returns every project of the account as separate bundles, handy when you want to copy the whole list into a sheet or review them all in one place.

The listed modules stay close to projects. For anything else the Smartcat API offers, Make an API Call reuses the same connection. The Smartcat page in the Make docs also warns that it was generated with AI from vendor documentation, so check important details with Smartcat directly. If you are still choosing a tool, read the Make review or the n8n vs Make comparison, and the Make pricing page explains how plans count usage.

Connect

How do you connect Smartcat to Make?

  1. 01

    Create an API key in Smartcat

    Log in with a company account that has administrator access. Open Settings then API, copy the Account ID shown on screen, click Create New Key in the API Keys pane and copy the key that appears.

  2. 02

    Add a Smartcat module in Make

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

  3. 03

    Paste your credentials

    Give the connection a clear label in Connection name if you like (this field is optional), paste the Account ID and the API key you copied, then save. Make can now read your projects.

First scenario

Your first scenario: clear out finished projects

GoalWhen a project is completed in Smartcat, Make deletes it so your project list only shows active work.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module. Search for Smartcat and pick Watch Completed Project.

  2. 02

    Link your account

    Click Create a connection and enter the Account ID and API key from Smartcat. Once saved, the module can read your projects and the connection is ready for the next module too.

  3. 03

    Add the deletion

    Click the + on the right of the trigger and choose Delete a Project. Map the project coming from the trigger, so Make removes exactly the one that was just completed.

  4. 04

    Test on a sample project

    Complete a throwaway project in Smartcat, then click Run once. Open the bubbles above each module to read the bundles they received and confirm that only the test project went away.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set how often Make checks (every 15 minutes by default, which is also the shortest interval on the Free plan), then turn the scenario on.

Triggers

What starts a Smartcat scenario

1 module starts a scenario when something happens in Smartcat. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Smartcat as soon as it happens.

Smartcat1Watch Completed Project

Watch Completed Project

Scheduled trigger

In Make“Triggers when a project is completed.”

Watch Completed Project starts your scenario when Make finds a Smartcat project that has been completed since its last check. Each finished project becomes one bundle for the modules that follow.

How it fires
scheduled. Make checks Smartcat on the scenario's schedule, so a project finished just after a check waits for the next run.
When to use it
as the starting point of any scenario that should follow a delivery, such as telling the account manager or archiving the project.
Watch out
only completed projects come through; a project still in translation never reaches the scenario, so test with one you have actually closed.
Modules

Everything else Smartcat can do in Make

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

Smartcat1

Delete a Project

Action

In Make“Removes a project.”

Delete a Project removes one project from your Smartcat account, which keeps the workspace focused on jobs that are still moving. You point it at the project to remove, usually mapped from an earlier module.

When to use it
right after Watch Completed Project, when finished projects only clutter the list for your linguists.
Watch out
treat a deletion as final and always run your first test on a project you can afford to lose.
Smartcat2

Get a Project

Action

In Make“Gets a project.”

Get a Project fetches a single Smartcat project so its details become available to the modules after it. It works on one project at a time, usually the one mapped from a previous step.

When to use it
when you already know which project matters, for example the one a trigger just handed over, and you need its information further down the scenario.
Watch out
to go through many projects, start with List Projects instead.
Smartcat3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Smartcat API from inside your scenario, with the same connection as the other modules. It is the way to cover what the four ready-made modules leave out.

When to use it
when you need something beyond projects, or a detail the listed modules do not expose.
Watch out
you describe the request yourself, so keep the Smartcat API documentation open and test the call with Run once before relying on it.
Smartcat4

List Projects

Search

In Make“Lists all projects.”

List Projects returns the projects of your Smartcat account, each one as its own bundle, so you get a full picture instead of a single record. As a search, it can send back zero, one or many results.

When to use it
when you want to copy every project into a spreadsheet or review the whole account in one place.
Watch out
each returned project runs the following modules once, and every run uses operations on your plan.
Need help

Need help automating Smartcat with Make?

A person reads every message.

FAQ

Smartcat and Make: common questions

01Is the Smartcat Make integration free?
Yes, on the Make side. Smartcat is a standard app, so its modules are available from the Free plan onward. 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) lower the interval to 1 minute, lift the limit on active scenarios and count usage in credits per month. You still need your own Smartcat subscription, which Smartcat prices separately.
02What do you need to connect Smartcat to Make?
You need a Smartcat company account with administrator access and an API key. In Smartcat, go to Settings then API, copy the Account ID, click Create New Key and copy the generated key. In Make, add any Smartcat module, click Create a connection, optionally name it, and paste both values. The connection is then shared by every Smartcat module in your scenarios, so you only set it up once per account.
03Does the Smartcat trigger in Make react in real time?
No. Watch Completed Project is a scheduled trigger, which means Make checks Smartcat at the interval set on the scenario rather than being alerted by Smartcat the second a project is finished. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval, while paid plans can go down to 1 minute. For most delivery follow ups that delay is fine, but plan for it if someone is waiting on the result.
04What if the Smartcat module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Smartcat API with the connection you already created, so you can reach features the four ready-made modules do not cover, such as anything beyond projects. You write the request yourself, so keep the Smartcat API documentation next to you and test with Run once. Note that the Smartcat page in the Make docs is marked as AI generated, so confirm key details with Smartcat.
05Should you use Make or n8n for Smartcat?
It depends on what you need to build. In Make, Smartcat comes with 5 modules, a scheduled trigger for completed projects and Make an API Call for the rest, and it works from the Free plan. The same app often has a node in n8n as well, so check what that node covers before you decide. Compare the modules each side offers against the scenario you have in mind, then test the one that fits with a real project.
Same platform

Other docs you might need on this stack.

Browse all integrations