Resources · Make integration

Delesign Make integrationAutomate Delesign with Make.

Can your Delesign projects start themselves when a request lands somewhere else? The Delesign Make integration gives you 7 modules: 6 actions and 1 search around projects and messages. This page walks you through the connection, a first scenario and what each module is good for.

Try the Delesign integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Delesign Make integration actually do?

The Delesign Make integration links your Delesign account to Make, so a scenario (the automation you build in Make, a chain of modules) can create, read, update, search and delete Delesign projects, and post messages, without you opening Delesign. The other apps in the chain decide when that happens.

Requests that turn into projects. A client fills a form in another app, and Create a Project opens the matching project in Delesign, with the details mapped from the form. Nobody retypes the brief.

Status that follows your pipeline. When a deal moves in your CRM, Search Projects finds the right project and Update a Project changes it, so Delesign reflects what sales already know.

Cleanup you control. A cancelled order can reach Delete a Project. Keep that one behind a filter: a deleted project does not come back.

Delesign has no trigger in Make, so something else has to start the scenario: another app, or the schedule you set on the first module. For endpoints the listed modules skip, Make an API Call reuses the same connection. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make training covers scenario building from scratch, and Make troubleshooting helps when a run fails.

Connect

How do you connect Delesign to Make?

  1. 01

    Copy your API token in Delesign

    You need an active Delesign account. Open the account settings page, go to the developers section and copy the API token shown on screen. Keep it at hand, Make asks for it in the next step.

  2. 02

    Add a Delesign module in Make

    In your scenario, add any Delesign module and click Create a connection. A connection is your Delesign account linked to Make once, then reused by every Delesign module. The Connection name field is optional; a clear name helps if you manage several accounts.

  3. 03

    Paste the token and save

    Paste the API token you copied, or follow the on-screen instructions, and save. Make can now read your Delesign projects, which means dropdowns fill with real data instead of empty boxes.

First scenario

Build your first scenario with Delesign

GoalWhen a new request arrives in another app, Make creates a Delesign project and posts a message about it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where requests arrive (a form or CRM tool), since Delesign has no trigger of its own.

  2. 02

    Add Create a Project

    Click the + on the right of that first module, search for Delesign and choose Create a Project. Select your connection, then map the request details from the first module into the project fields.

  3. 03

    Add Create a Message

    Add Create a Message after the project module. Map the project returned by the previous module and write the text, so the new project comes with context from the start.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles (the items passed from module to module) each step received. Check in Delesign that the project and the message look right.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Save, then switch the scenario on.

Modules

What each Delesign module does

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

Delesign1

Create a Message

ActionIn the docs only

Posts a message in Delesign from your scenario, going by its name. A note or an update then reaches Delesign, and nobody has to type it by hand.

When to use it
right after a project is created or changed, to pass on the context that came from the form or the CRM.
Watch out
the documentation gives no field details for this module, so run it once on a test project before you trust the mapping.
Delesign2

Create a Project

ActionIn the docs only

Opens a new project in Delesign with values mapped from earlier modules, which turns an incoming request into work that is ready to be picked up.

When to use it
a client submits a brief elsewhere and you want the project to exist before anyone reads the email.
Watch out
each run creates one more project, so a duplicated form entry means a duplicated project; filter upstream if that can happen.
Delesign3

Delete a Project

ActionIn the docs only

Removes a Delesign project for good, which keeps your workspace free of requests that were cancelled or entered by mistake.

When to use it
an order is cancelled in your shop or CRM and the matching project should disappear with it.
Watch out
a deletion does not come back. Put a filter before this module and test it with Run once on a throwaway project first.
Delesign4

Get a Project

ActionIn the docs only

Reads one project you already know and hands its details to the next modules, so they work on current data rather than on what the request said.

When to use it
you stored the project reference earlier and need its latest state before sending a message or an update.
Watch out
it needs one precise project; without its reference, start with Search Projects instead.
Delesign5

Make an API Call

ActionIn the docs only

Calls any endpoint of the Delesign API with the connection you already set up, which covers whatever the six other modules leave out.

When to use it
you need something from Delesign that no listed module offers, and you have the API reference open next to you.
Watch out
you pick the endpoint yourself, and the Make documentation for Delesign is AI-generated, so confirm it with Delesign first.
Delesign6

Search Projects

SearchIn the docs only

Finds Delesign projects and returns them as separate bundles, which lets the next modules act on each match in turn.

When to use it
you do not have the project reference at hand and you want to update or message the right one.
Watch out
a search can return zero, one or several projects; every bundle runs the following modules, and each run counts as an operation.
Delesign7

Update a Project

ActionIn the docs only

Changes an existing Delesign project with new values from your scenario, keeping it in line with what happens in your other tools.

When to use it
a deal changes stage or a client edits the request, and Delesign should show the new version without a manual edit.
Watch out
it acts on one project, so feed it a single reference from Get a Project or a filtered Search Projects.
Need help

Need help automating Delesign with Make?

A person reads every message.

FAQ

Delesign and Make: common questions

01Is the Delesign Make integration free?
Yes, on the Make side. Delesign is a standard app, available from the Free plan. That plan allows 2 active scenarios, a shortest schedule of 15 minutes, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations, one per module per bundle. You still need an active Delesign account of your own.
02What does it take to connect Delesign to Make?
An active Delesign account and its API token. In Delesign, open the account settings, go to the developers section and copy the token. In Make, add a Delesign module, click Create a connection, give it a name if you want, paste the token and save. The connection is then reused by all 7 Delesign modules. The Make documentation for this app is flagged as AI-generated, so if a screen differs, follow what Delesign shows and ask Delesign directly.
03Does the Delesign Make integration have a real-time trigger?
No. Delesign has no trigger module in Make, neither scheduled nor instant. A scenario that uses Delesign starts from another app, for example a form or a CRM module that reacts to new entries, or from the schedule you set on the first module, every 15 minutes by default. Delesign modules then act further down the chain. To test without waiting, click Run once and the scenario runs one time on the spot.
04What if a Delesign module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Delesign API with the connection you already created, so there is no second login. The 7 listed modules cover projects (create, get, search, update, delete) and messages; anything beyond that goes through this module, with the API reference as your guide. Since the Make documentation for Delesign is AI-generated and may contain mistakes, confirm the endpoint with Delesign before building on it.
05Make or n8n for Delesign: which one fits?
It depends on what you already run. In Make, Delesign comes with 7 ready modules and Make an API Call, a visual editor and a Free plan to test on. n8n often has nodes for the same apps, so check whether one exists for Delesign before deciding. Compare on the criteria that matter to you: the modules you need, where your other apps already live, and who on the team will maintain the scenario. Neither tool is ranked here.
Same platform

Other docs you might need on this stack.

Browse all integrations