Resources · Make integration

Restya Core Make integrationAutomate Restya Core with Make.

Can Make keep your Restya Core projects moving without anyone copying tasks by hand? The Restya Core Make integration gives you 11 modules: 6 triggers that watch tasks, comments, activity and members, and 5 actions that write back. This guide connects your account and walks you through a first scenario.

Try the Restya Core integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Restya Core Make integration do?

The Restya Core Make integration links your Restya Core account to Make, a no-code tool where you build a scenario: a chain of modules that runs by itself. Each module is one brick. Here, six of them notice changes in Restya Core and five of them create tasks, projects, comments and labels for you.

Onboard people once they join. Watch New Members of the Project spots a new teammate, and Create a Task hands them a first task in the same project. Nobody has to remember the welcome checklist.

Sort incoming work without opening the board. Watch New Tasks picks up each new task, and Add Label to Task tags it so the right people see it. Pair it with a form tool such as the 123FormBuilder Make integration and Create a Task can turn a form entry into work in Restya Core.

Keep a written trail of what happens. Watch Task Comments and Watch New Activities of the Task follow the conversation on a task, while Create Task Comment or Create a Global Comment posts an update where the team already reads.

What to keep in mind: the official Make documentation for Restya Core is limited, because there is not much public information about the app. The documentation gives no trigger type, so the six triggers are treated as scheduled, a deduction from their Watch names: this means Make checks for news on a timer instead of being told right away. If you are new to the editor, the Make training covers the basics, and the n8n vs Make comparison helps if you are weighing the two tools.

Connect

How do you connect Restya Core to Make?

  1. 01

    Add a Restya Core module

    Open your scenario, add any Restya Core module and click Create a connection. A connection is your Restya Core account linked to Make once; every Restya Core module in your scenarios reuses it afterwards.

  2. 02

    Name the connection

    Give the connection a name if you like. It is optional, yet handy when you manage more than one Restya Core account, for instance a test space and the one your team works in every day.

  3. 03

    Authorize and save

    Authorize Make on the Restya Core page that opens, or paste the key Restya Core gives you, then click Save. Make now lists the items it can read in your account when you fill a module.

First scenario

Build your first scenario with Restya Core

GoalWhen someone joins a project in Restya Core, Make creates a starter task for them in that project.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big + in the middle of the editor to place your first module.

  2. 02

    Pick the trigger

    Search for Restya Core, choose Watch New Members of the Project and select your connection. Fill its fields: once the connection exists, Make lists what it can read in your account.

  3. 03

    Add the task

    Click the + on the right of the trigger and add Create a Task. Map the new member from the trigger into the task so the person knows it is theirs.

  4. 04

    Test with Run once

    Add a colleague to the project, then click Run once. Open the bubble above each module to read the bundle it received, one item handed from module to module.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; on the Free plan that is also the shortest gap. Switch the scenario on and it keeps going.

Triggers

Which Restya Core triggers can start a scenario?

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

Restya Core1Watch Global Comments

Watch Global Comments

triggerIn the docs only

This trigger hands you every new global comment in Restya Core, so a remark posted outside a single task still reaches the people who need it. Each comment arrives as its own bundle for the next module.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
your team posts announcements as global comments and you want each one copied to a chat channel or logged somewhere else.
Watch out
the documentation is limited, so run the scenario once and read the bundle before you map anything.
Restya Core2Watch New Activities

Watch New Activities

triggerIn the docs only

Think of it as a feed of everything that moves in your Restya Core account: Make collects new activities and starts your scenario with them. It is the widest net among the six triggers.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
you want a running log of changes in a spreadsheet or a report, without choosing one task first.
Watch out
a busy account produces many bundles, and each module that handles one costs an operation on your plan, so add a filter early.
Restya Core3Watch New Activities of the Task

Watch New Activities of the Task

triggerIn the docs only

Where Watch New Activities covers the whole account, this one zooms in on a single task and reports what changes on it. You follow one piece of work closely without the noise from everything else.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
a key deliverable is running and a manager wants a message each time something happens on that task.
Watch out
the documentation gives no detail on how the task is chosen, so check the module fields and test with Run once before you rely on it.
Restya Core4Watch New Members of the Project

Watch New Members of the Project

triggerIn the docs only

You learn who just joined a project, and your scenario can greet them, assign work or tell the rest of the team. Each newcomer comes through as one bundle.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
a freelancer or a new hire is added to a client project and should get a starter task without anyone thinking about it.
Watch out
the member appears after the next scheduled check, not the second they are added, so warn the person if the welcome task arrives a bit later.
Restya Core5Watch New Tasks

Watch New Tasks

triggerIn the docs only

Every task created in Restya Core can kick off a scenario, which makes this the natural starting point for routing, labeling or reporting on fresh work.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
requests land as tasks and you want each one labeled with Add Label to Task or announced in the tool your team reads.
Watch out
if the same scenario also runs Create a Task, it will pick up its own tasks on the next check and keep feeding itself, so send new tasks to a different place.
Restya Core6Watch Task Comments

Watch Task Comments

triggerIn the docs only

Comments written on tasks come back to Make one by one, so the discussion around the work can travel beyond Restya Core. Global comments stay with Watch Global Comments.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
clients or teammates answer in task comments and you want each reply forwarded by email or saved in a customer file.
Watch out
pairing it with Create Task Comment on the same tasks can make the scenario answer its own comments, so add a filter that skips them.
Modules

What can Make do in Restya Core?

Restya Core gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Restya Core1

Add Label to Task

ActionIn the docs only

You get tasks that are tagged the moment they need it, so the board is already sorted when someone opens it. The module puts a label on one existing task.

When to use it
right after Watch New Tasks, to mark urgent requests or tag work by client.
Watch out
it works on a task that exists, so map the task from an earlier module.
Restya Core2

Create Task Comment

ActionIn the docs only

The update lands on the task itself, where the people doing the work already look. Make writes a comment on one task with text you build from earlier modules.

When to use it
a payment is confirmed or a file is signed elsewhere and the task should say so.
Watch out
avoid it in a scenario started by Watch Task Comments on the same tasks.
Restya Core3

Create a Global Comment

ActionIn the docs only

This posts a message that is not tied to a single task, useful when news concerns the whole team rather than one piece of work.

When to use it
a new project starts or a milestone closes and everyone should read it in Restya Core.
Watch out
pick Create Task Comment instead when the note belongs to one task, or it will get lost.
Restya Core4

Create a Project

ActionIn the docs only

A new project appears in Restya Core without anyone setting it up by hand, ready for the tasks that follow. It is the biggest building block among the actions.

When to use it
a deal is signed in your sales tool and delivery needs its own project.
Watch out
run it once per event, because a repeated run creates a second project with the same content.
Restya Core5

Create a Task

ActionIn the docs only

Work that starts somewhere else becomes a real task in Restya Core, with the details mapped from the modules before it. No more retyping requests.

When to use it
a form entry, an email or a new project member should turn into a task someone owns.
Watch out
do not start this scenario with Watch New Tasks on the same project, or each new task triggers the next.
Need help

Need help automating Restya Core with Make?

A person reads every message.

FAQ

Restya Core Make integration: common questions

01Is the Restya Core Make integration free?
Yes, you can start on the Make Free plan, because Restya Core is a standard app and not one reserved to the Enterprise plan. The Free plan gives you 2 active scenarios, a shortest gap 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 gap to 1 minute and lift the cap on active scenarios. Usage is counted in operations, one per module per bundle.
02What do you need to connect Restya Core to Make?
A Restya Core account and a Make account. The Make documentation lists no other prerequisite. You add a Restya Core module, click Create a connection, optionally name it, authorize Make on the Restya Core page or paste the key the app gives you, and click Save. The connection is then reused by every Restya Core module in your scenarios. Since the documentation for this app is limited, test with Run once before relying on the scenario.
03Do Restya Core triggers fire instantly in Make?
No. The documentation does not state the trigger type, but their Watch names point to scheduled triggers, which means Make checks the app on the scenario's schedule instead of being called by Restya Core the moment something happens. A new scenario checks every 15 minutes by default, and that is also the shortest interval on the Free plan. Paid plans allow a check every minute. If a gap between the event and the reaction matters, set the schedule on the first module to match.
04What if the Restya Core module you need is missing in Make?
It depends on what is missing. The Restya Core app in Make has no Make an API Call module, so you cannot reach the rest of the API from Make directly. You can often get close by combining the 11 existing modules, for example creating a task and then labeling it. If that is not enough, another app in your stack may hold the data you need, or the Hack'celeration team can look at your case and suggest a workable route.
05Should you use Make or n8n for Restya Core?
It depends on your criteria, not on a winner. Make gives you 11 Restya Core modules in a visual editor, six scheduled triggers and five actions, with no code to write. The same app often has an n8n node too, so check which modules each tool offers for the tasks, comments and projects you want to automate. Pick the tool whose modules cover your scenario and whose editor your team is comfortable with.
Same platform

Other docs you might need on this stack.

Browse all integrations