Resources · Make integration

Google Cloud Dialogflow ES Make integrationAutomate Google Cloud Dialogflow ES with Make.

Can Make answer your Dialogflow agent while the user is still talking? The Google Cloud Dialogflow ES Make integration offers 26 modules, with 1 instant trigger for fulfillment. This page shows how to link your Google Cloud project and build a first reply flow.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Google Cloud Dialogflow ES Make integration do?

The Google Cloud Dialogflow ES Make integration links your Dialogflow agent to a Make scenario, the automation you build as a chain of modules. When a user query matches an intent (a type of request the agent recognizes) with webhook enabled, Make receives it, runs your logic, and can send the answer back. Other modules manage intents, entities, contexts and agents without opening the console.

Answers built from your own data. Watch for Fulfillment receives the matched query, the modules in between look up what the user asked for, and Response to Fulfillment returns the text to the agent. The reply has a strict deadline: 10 seconds for Google Assistant applications, 5 seconds for all others.

An agent maintained from a spreadsheet or a form. Create an Intent, Update an Intent and Create Entities let a scenario feed new training content into the agent, so the person who knows the product edits a sheet instead of the console. List Intents and List Entity Types show what already exists before you add more.

Text understood outside the chat widget. Detect an Intent sends any sentence to the agent and gets the matched intent back, which helps classify an incoming email or a form message before routing it.

What the listed modules do not cover, Make an API Call reaches with the same connection. The same app often has an n8n node too; the n8n vs Make page lays out the criteria. If you prefer to learn the editor step by step, the Make training starts from zero, and the Make review covers the plans.

Connect

How do you connect Google Cloud Dialogflow ES to Make?

  1. 01

    Add a module and open the connection window

    In your scenario, add any Google Cloud Dialogflow ES module and click Create a connection. A connection is your Google Cloud account linked to Make once and reused by every Dialogflow module afterwards.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name such as the project of your agent helps when you run several agents from the same Make account.

  3. 03

    Enter your credentials

    Follow the on-screen instructions, or paste the Client ID and Client secret created under APIs and services then Credentials in the Google Cloud Console, in the project tied to your agent.

First scenario

Your first scenario: reply to a Dialogflow fulfillment request

GoalWhen a user query matches an intent with webhook enabled in Google Cloud Dialogflow ES, Make builds the answer and sends it back to the agent.

  1. 01

    Create the scenario

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

  2. 02

    Add Watch for Fulfillment

    Search for Google Cloud Dialogflow ES, pick Watch for Fulfillment, click Create a webhook, then Create a connection. It carries the lightning badge: the agent calls Make as soon as a query matches.

  3. 03

    Add Response to Fulfillment

    Click the + on the right of the trigger, choose Response to Fulfillment and map the reply text. Each item passed along here is a bundle, one matched query at a time.

  4. 04

    Test with Run once

    Click Run once, then send your agent a phrase that matches an intent with webhook enabled. Read the bundles each module received and check the reply reached the conversation.

  5. 05

    Switch the scenario on

    Turn the scenario on. Since the trigger is instant, it waits for the agent's calls instead of running on a clock. Every module run counts as an operation on your plan.

Triggers

What starts a Dialogflow scenario

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

Google Cloud Dialogflow ES1Watch for Fulfillment

Watch for Fulfillment

Instant trigger

In MakeTriggers by a user query matched by intents with webhook enabled.

Watch for Fulfillment starts your scenario each time a user query lands on an intent where webhook is enabled, so Make gets the matched intent and can compute the answer the agent should give.

How it fires
instant: the app calls Make through a webhook as soon as it happens. No interval to set, the lightning badge on the module confirms it.
When to use it
an order status question where the answer sits in your own tools, not in the agent's static responses.
Watch out
only intents with webhook enabled reach Make; the others keep answering on their own.
Modules

Every Google Cloud Dialogflow ES module in Make

Google Cloud Dialogflow ES gives you 25 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Google Cloud Dialogflow ES1

Create a Context

Action

In MakeCreates a context in the specified session.

Opens a new context inside a conversation session, so the agent remembers what the user just talked about and steers the next turn toward the right intents.

When to use it
after a customer confirms an order number, add a context that keeps follow-up questions tied to that order.
Watch out
a context lives in one session, so pass the session of the current conversation, not a fixed value.
Google Cloud Dialogflow ES2

Create an Agent

Action

In MakeCreates an agent in the specified project.

Sets up a brand new Dialogflow agent in a Google Cloud project from a scenario, which saves clicking through the console when you spin up agents for several brands or clients.

When to use it
a new client signs and you want a blank agent ready in the project assigned to them.
Watch out
the agent lands in the project you pick, so check the connection points to the right one.
Google Cloud Dialogflow ES3

Create an Entity Type

Action

In MakeCreates an entity type in the specified agent.

Adds a new entity type to your agent, the category Dialogflow uses to recognize values like product names or cities in what users type.

When to use it
you launch a new product line and the agent must learn a fresh category of words to extract from questions.
Watch out
this creates the container only; fill it with Create Entities in the next module.
Google Cloud Dialogflow ES4

Create an Intent

Action

In MakeCreates an intent in the specified agent.

Writes a new intent into the agent, which lets the people who know your customers draft questions in a sheet and have Make push them into Dialogflow.

When to use it
the support team adds a row for a recurring question and the agent learns to recognize it.
Watch out
run List Intents first when rows can repeat, or you end up with two intents competing for the same phrases.
Google Cloud Dialogflow ES5

Create Entities

Action

In MakeCreates multiple entities in the specified entity type.

Adds several entities at once to an existing entity type, the fastest way to teach the agent a full catalog of values in a single operation.

When to use it
the store adds products and the agent should know each new name.
Watch out
the entity type must exist already; create it with Create an Entity Type or pick it from List Entity Types.
Google Cloud Dialogflow ES6

Delete a Context

Action

In MakeRemoves a context in the specified session.

Removes one context from a session, so the agent stops interpreting new messages through a topic the user has already closed.

When to use it
a customer cancels a booking mid-conversation and the booking context should no longer shape the next answers.
Watch out
once removed, the agent forgets that thread; add it back with Create a Context if the user returns to it.
Google Cloud Dialogflow ES7

Delete an Agent

Action

In MakeRemoves an agent in the specified project.

Removes an agent from its Google Cloud project, which helps you clean up test or retired agents as part of an offboarding scenario.

When to use it
a client contract ends and the agent built for them has to go along with the rest of their setup.
Watch out
there is no undo from Make; export what you need with Get an Agent before this module runs.
Google Cloud Dialogflow ES8

Delete an Entity Type

Action

In MakeRemoves an entity type in the specified agent.

Removes a whole entity type from the agent, so a category of values you no longer sell or support stops being extracted from user phrases.

When to use it
a discontinued range leaves your catalog and its category should disappear from the agent too.
Watch out
intents that relied on that type lose the value they used to capture, so review them first with List Intents.
Google Cloud Dialogflow ES9

Delete an Intent

Action

In MakeRemoves an intent and its followup intents in the specified agent.

Removes an intent from the agent, and its followup intents go with it, which keeps outdated answers from surfacing in conversations.

When to use it
a seasonal offer ends and the intent that described it should stop matching questions.
Watch out
the followup intents disappear too, so check with Get an Intent what hangs below before you delete.
Google Cloud Dialogflow ES10

Delete Entities

Action

In MakeRemoves multiple entities in the specified entity type.

Removes several entities from an entity type in one go, handy when your list of values shrinks and the agent should stop recognizing old names.

When to use it
products marked as withdrawn in your inventory tool should vanish from what the agent picks up.
Watch out
the entity type itself stays; use Delete an Entity Type to drop the whole category.
Google Cloud Dialogflow ES11

Detect an Intent

Action

In MakeProcesses a natural language query.

Sends a sentence in natural language to your agent and returns the intent it matches, which turns Dialogflow into a classifier for any text flowing through Make.

When to use it
an email or a web form message arrives and you want to know if it is a refund request, a quote or a complaint before routing it.
Watch out
the result is only as good as the intents already trained in the agent.
Google Cloud Dialogflow ES12

Get a Context

Action

In MakeRetrieves the details of a context in the specified session.

Reads the details of one context in a session, so your scenario knows what the agent currently holds about the conversation before choosing a reply.

When to use it
during fulfillment, check whether a shipping context is active before asking the user for an address again.
Watch out
you need the session and the context name; List Contexts shows which ones are there.
Google Cloud Dialogflow ES13

Get an Agent

Action

In MakeRetrieves the details of an agent in the specified project.

Fetches the settings of one agent in a project, useful as a snapshot to log or compare before a scenario changes anything on it.

When to use it
right before Update an Agent, store the current values in a sheet so you can restore them by hand.
Watch out
it returns one agent only, so pick the project that holds the agent you want.
Google Cloud Dialogflow ES14

Get an Entity Type

Action

In MakeRetrieves the details of an entity type in the specified agent.

Returns the details of one entity type, so a scenario can read which values the agent already knows before adding or removing any.

When to use it
compare the entity type with your product sheet to spot what is missing on either side.
Watch out
it targets a single type; to find its identifier, run List Entity Types first.
Google Cloud Dialogflow ES15

Get an Intent

Action

In MakeRetrieves the details of an intent in the specified agent.

Pulls the full details of one intent, which lets you audit or copy its content into a document where non technical colleagues can review it.

When to use it
a manager asks what the agent answers on refunds and you want the intent in a shared doc.
Watch out
one intent per operation; pair it with List Intents to walk through the whole agent.
Google Cloud Dialogflow ES16

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Calls any endpoint of the Dialogflow API with the connection you already set up, the way out when none of the listed modules covers what you need.

When to use it
a Dialogflow feature you rely on has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Dialogflow API reference open while you fill the module.
Google Cloud Dialogflow ES17

Response to Fulfillment

Action

In MakeResponds to the incoming fulfillment request. The response must occur within 10 seconds for Google Assistant applications or 5 seconds for all other applications, otherwise the request will time out.

Sends the answer your scenario built back to the agent, which then says it to the user as if it came from Dialogflow itself.

When to use it
it closes every scenario that opens with Watch for Fulfillment.
Watch out
the reply must arrive within 10 seconds for Google Assistant applications and 5 seconds for every other one, otherwise the request times out, so keep slow steps out of the path.
Google Cloud Dialogflow ES18

Update a Context

Action

In MakeUpdates a context in the specified session.

Changes an existing context in a session, so the agent keeps the conversation on track when the user corrects something they said earlier.

When to use it
a customer switches the delivery city mid-chat and the context should carry the new value.
Watch out
the context must exist in that session; otherwise start with Create a Context.
Google Cloud Dialogflow ES19

Update an Agent

Action

In MakeUpdates an agent in the specified project.

Edits the settings of an existing agent from a scenario, which keeps several agents aligned without repeating the same clicks in each console project.

When to use it
a change decided for all your brands must reach every agent they run.
Watch out
the change applies straight away; read the current state with Get an Agent before you overwrite it.
Google Cloud Dialogflow ES20

Update an Entity Type

Action

In MakeUpdates an entity type in the specified agent.

Modifies an entity type that already exists, so the category stays in step with how your business names things without rebuilding it.

When to use it
a product family is renamed and the entity type should follow the new wording.
Watch out
to add or remove single values, Create Entities and Delete Entities are the more precise choice.
Google Cloud Dialogflow ES21

Update an Intent

Action

In MakeUpdates an intent in the specified agent.

Rewrites an intent already in the agent, which lets the team refine phrases or answers from a sheet and see the agent pick them up.

When to use it
a reviewed answer gets approved in your content tool and must replace the old one in Dialogflow.
Watch out
fetch the intent with Get an Intent first so you do not wipe parts you meant to keep.
Google Cloud Dialogflow ES22

List Contexts

Search

In MakeLists all contexts in the specified session.

Returns every context active in a session, one bundle each, so a scenario can see at a glance where the conversation stands.

When to use it
before handing a chat to a human agent, collect the active contexts and add them to the support ticket.
Watch out
an empty result is normal when nothing is active; plan a path for zero bundles.
Google Cloud Dialogflow ES23

List Entities

Search

In MakeLists all entities in the specified entity type.

Returns all the entities of one entity type, which gives you the full list of values the agent recognizes to compare against your source of truth.

When to use it
sync check between your catalog and the agent before a product launch.
Watch out
each entity becomes its own bundle, and every following module then runs once per bundle.
Google Cloud Dialogflow ES24

List Entity Types

Search

In MakeLists all entity types in the specified agent.

Lists every entity type defined in the agent, the starting point when a scenario must find the right category before touching its values.

When to use it
you manage several agents and need the identifier of the product type in each one.
Watch out
it can return many bundles; add a filter after it to keep only the type you want.
Google Cloud Dialogflow ES25

List Intents

Search

In MakeLists all intents in the specified agent.

Returns all intents of the agent, one bundle per intent, a quick way to export the agent or check whether a question is already covered.

When to use it
before Create an Intent, look for a similar one so the agent does not end up with duplicates.
Watch out
on a large agent this means many operations downstream, so filter early.
Need help

Need help automating Google Cloud Dialogflow ES with Make?

A person reads every message.

FAQ

Questions about Google Cloud Dialogflow ES and Make

01Is the Google Cloud Dialogflow ES Make integration free?
Yes, on the Make side: Google Cloud Dialogflow ES is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of up to 5 minutes and files up to 5 MB. Paid plans such as Core, Pro, Teams and Enterprise lower the interval to 1 minute and count usage in credits each month. The Dialogflow side follows Google Cloud pricing, which is set by Google, not Make.
02What is needed to connect Google Cloud Dialogflow ES to Make?
A Google Cloud account with the Dialogflow API enabled and the right permissions on the project that holds your agent. In Make, add a Dialogflow module and click Create a connection, or Create a webhook first for the trigger. You can follow the on-screen instructions, or create an OAuth client ID under APIs and services, Credentials in the Google Cloud Console and paste the Client ID and Client secret. Pick the project that holds your agent before you create anything.
03Does the Dialogflow ES trigger in Make react in real time?
Yes. Watch for Fulfillment is an instant trigger: Dialogflow calls Make through a webhook as soon as a user query matches an intent with webhook enabled, so there is no polling interval to wait for. Intents without webhook enabled never reach Make. If your scenario answers with Response to Fulfillment, keep it quick, because the reply must arrive within 10 seconds for Google Assistant applications and within 5 seconds for the rest.
04What if a Dialogflow ES module is missing in Make?
It depends on the gap. Google Cloud Dialogflow ES has Make an API Call, which reaches any endpoint of the Dialogflow API with the same connection you already use, so a feature without its own module is still within reach. You write the request yourself, which asks for a look at the Dialogflow API reference. For timeouts on fulfillment, the only documented limit is the reply window of 10 seconds for Google Assistant and 5 seconds elsewhere.
05Make or n8n for Google Cloud Dialogflow ES?
It depends on your criteria. Make gives you 26 ready modules for this app, an instant trigger for fulfillment and Make an API Call for the rest, all built visually with Run once to test. The same app often has an n8n node as well. Compare what each tool offers for the exact modules you need and the way your team prefers to build, then pick the one your team will actually maintain.