Resources · Make integration

Dify Make integrationAutomate Dify with Make.

Want your Dify apps to answer the tools your team already uses? The Dify Make integration gives you 3 action modules: run a workflow, send a chat message, or call any endpoint. This guide walks you through the API key, the connection and a first working scenario.

Try the Dify integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Dify Make integration let you do?

The Dify Make integration lets a Make scenario (the automation you build in Make, a chain of small steps) call the apps you built in Dify. Make sends the input, Dify does the AI work, and the answer comes back into the scenario so the next step can store it, send it or act on it.

Put a Dify workflow behind a form. A new request lands in another app, and Execute a Workflow hands it to the workflow you designed in Dify. The output flows on to your CRM or your spreadsheet, without anyone copying text between tabs.

Let a Dify assistant reply where questions arrive. Pass an incoming message to Send a Chat Message and route the answer back to the channel it came from. Your support or sales team keeps the conversation in the tool it already watches.

Reach the parts of Dify the modules skip. Make an API Call hits any endpoint of the Dify API with the same connection, so a missing module does not stop the project.

Know the limits before you start. Dify has no trigger in Make, so something else has to start the scenario: a schedule, or an event in another app. Make itself flags its Dify documentation as AI-generated and possibly wrong, so check field names against Dify's own docs. If you are weighing tools, the n8n vs Make comparison lays out the differences, Make pricing explains what each plan allows, and the Make training covers scenario building step by step.

Connect

How do you connect Dify to Make?

  1. 01

    Generate an API key in Dify

    Log in to Dify and open the Applications section. Pick the app you want Make to use, click Access API, generate a key if none exists yet, and copy it. Make needs this key to talk to that app.

  2. 02

    Add a Dify module and create the connection

    In your scenario, add any Dify module and click Create a connection. A connection is your Dify account linked to Make once, then reused by every Dify module. You can fill Connection name so you recognize it later.

  3. 03

    Paste the key and save

    Paste the API key you copied from Dify, or follow the instructions Make shows on screen, then save. The connection now appears in the module, and the other Dify modules of the scenario can pick it from the list.

First scenario

Your first scenario with Dify and Make

GoalWhen the scenario starts, Make runs a Dify workflow, then sends its output to a Dify chat app for a follow-up answer.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor. Each circle you add is a module: one brick of the scenario.

  2. 02

    Add Execute a Workflow

    Search for Dify, choose Execute a Workflow and click Create a connection with your API key. Fill the fields the module shows; Make lists what it can read once the connection works.

  3. 03

    Chain Send a Chat Message

    Click the + on the right of the first module and pick Send a Chat Message. Map the workflow result into the message, so each bundle (one item passed between modules) carries real data.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time, and you can read the bundles each module received. Open them to check that Dify returned what you expected.

  5. 05

    Schedule it and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then turn the scenario on. Each module run counts as one operation on your Make plan.

Modules

What the Dify modules do

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

Dify1

Execute a Workflow

ActionIn the docs only

This module starts a workflow you built in Dify and brings its output back into Make, ready for the next module. It turns a Dify flow into a step you can place anywhere in a scenario.

When to use it
your Dify app is a fixed pipeline, such as summarizing a document or classifying a request, and you want one result per input.
Watch out
the connection uses the key of one Dify application, so point it at the app that holds the workflow.
Dify2

Make an API Call

ActionIn the docs only

Here you get a way to reach any endpoint of the Dify API from your scenario, reusing the Dify connection you already created. No second login, no separate key to manage.

When to use it
the action you need is in the Dify API but has no dedicated module in Make.
Watch out
you write the request yourself, so keep Dify's API reference open and test it with Run once before going live.
Dify3

Send a Chat Message

ActionIn the docs only

With this one, a message from your scenario reaches a Dify chat app, and the reply comes back as data you can map into the next module. Think of it as a conversation turn you trigger from Make.

When to use it
a question arrives in another tool, like an inbox or a help desk, and your Dify assistant should draft the answer.
Watch out
Make marks its Dify documentation as AI-generated, so check each field against Dify's own docs.
Need help

Need help automating Dify with Make?

A person reads every message.

FAQ

Questions about the Dify Make integration

01Is the Dify Make integration free?
Yes, on the Make side. Dify is a standard app, so its modules are available on the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to one minute and remove the cap on active scenarios. Your Dify subscription is a separate matter: Make points you to the Dify pricing page for that part.
02What do you need to connect Dify to Make?
You need an active Dify account and an API key generated from the application you want to use. In Dify, open the Applications section, select the app, click Access API and generate a key if there is none yet, then copy it. In Make, add a Dify module, click Create a connection, give it a name if you like and paste the key. That single connection is then shared by every Dify module in your scenarios, so you only do this once per application.
03Can Dify start a Make scenario by itself?
No. The Dify app in Make has no trigger, only 3 action modules, so the scenario needs another starting point. You can put a Dify module first and let the schedule start it, every 15 minutes by default, with 15 minutes as the floor on the Free plan and one minute on paid plans. Or you can open the scenario with a trigger from another app, such as a new form entry or an incoming email, and place the Dify module right after it.
04What if the Dify module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Dify API with the connection you already have, so you are not limited to Execute a Workflow and Send a Chat Message. You will have to build the request from Dify's API reference, which takes a bit more care than a ready-made module. Also keep in mind that Make flags its Dify documentation as AI-generated and possibly inaccurate, so confirm field names in Dify's own documentation before relying on them.
05Should you use Make or n8n for Dify?
It depends on the tool your team already works in. In Make, Dify comes with 3 modules: Execute a Workflow, Send a Chat Message and Make an API Call, which covers the rest of the Dify API with the same connection. Apps listed in Make often have an n8n node too, so check whether n8n offers one for Dify before deciding. Then compare how each tool handles the rest of your scenario, the apps around Dify, and the plan limits that apply to your volume.
Same platform

Other docs you might need on this stack.

Browse all integrations