DEV Community: Flowpaja

Make.com OAuth redirect URLs: the integromat.com callbacks, your own Google client and HTTP OAuth 2.0

Flowpaja — Sat, 17 Oct 2026 18:02:14 +0000

Short answer: when you create your own OAuth client for Make, the redirect URL (callback URL) depends on the app, and most of them still start with www.integromat.com/oauth/cb/, from before Integromat became Make. The ones people search for most:

HTTP › Make a request (OAuth 2.0): https://www.integromat.com/oauth/cb/oauth2
Google Drive: https://www.integromat.com/oauth/cb/google-restricted
Google Sheets, Calendar, Forms, Contacts: https://www.integromat.com/oauth/cb/google/
Gmail: https://www.make.com/oauth/cb/google-email

Google only accepts an exact match, including the trailing slash. Copy the address character for character from the table below or from the app's page in Make's docs. A wrong or missing one gives Error 400: redirect_uri_mismatch.

This guide contains an affiliate link, marked “affiliate link”.

Checked on 3 October 2026: every redirect URL on this page is copied from Make's own documentation: the app pages on apps.make.com (most updated 2 October 2026), Make's Help Center and Make's developer docs. Google rules and error texts come from Google's OAuth 2.0 documentation and Google Cloud Help, with their update dates in the sources list. We haven't tested every app ourselves. We earn affiliate commissions from Make.

Do you need your own OAuth client at all?

Usually not. For most apps you click Create a connection, sign in, and Make uses its own built-in OAuth client. In that case there's no redirect URL to enter anywhere. You need one only in these cases:

Google Drive with a personal account. Make's Google Drive docs say: "To connect an email ending in @gmail or @googlemail, you need to create a custom OAuth client in the Google Cloud Platform". For other domains it's optional.
The HTTP app with OAuth 2.0. HTTP › Make a request has no built-in client, so you always bring your own. That's how you call an API that Make has no module for.
You choose to. Many apps, including Gmail, Google Sheets, Dropbox, Shopify and Microsoft Teams, have an optional advanced setting (Advanced settings or Show advanced settings) for your own Client ID and Client Secret. Make's Help Center mentions "Google Workspace users who prefer to use a custom OAuth client". For Gmail and Sheets, Make's docs mark it as optional.
A custom app you build in Make's developer platform. Custom apps have their own callback URLs (see below).

What "google-restricted" means. Make's Help Center says: "To connect some restricted Google services, like Google Drive or Google Sheets, to Make, you need to create your own project in Google Cloud Platform and a custom OAuth client." Google classes the full Drive scope (auth/drive) and most Gmail scopes (gmail.readonly, gmail.compose, gmail.modify) as restricted. Restricted scopes "provide wide access to Google user data and require restricted scope OAuth App Verification" (Google's Gmail scopes page, updated 10 September 2026). Make's Drive connection, the older Gmail (legacy) app and Google Groups use the google-restricted callback. Make's error messages call it a "Google Restricted connection".

Affiliate disclosure: the link marked "affiliate link" includes our partner code. If you sign up or later buy a paid plan through it, Flowpaja may earn a commission at no extra cost to you. Don't have an account yet? Create a free Make account (affiliate link). More on the tools we use: best tools for Make automation.

Start with the existing setup reference Use the live error cheat sheet to identify the failure and inspect the last completed action.

Open the free reference

Google apps: redirect URLs as Make documents them

Make app	Authorized redirect URI
Gmail (current version)	`https://www.make.com/oauth/cb/google-email`
Gmail (legacy)	`https://www.integromat.com/oauth/cb/google-restricted`
Google Drive	`https://www.integromat.com/oauth/cb/google-restricted`
Google Groups	`https://www.integromat.com/oauth/cb/google-restricted/`
Google Sheets, Google Calendar, Google Forms, Google Contacts, Google BigQuery	`https://www.integromat.com/oauth/cb/google/`
Google Docs, Google Slides, Google Analytics	`https://www.integromat.com/oauth/cb/google` (no trailing slash)
Google Analytics 4	`https://www.integromat.com/oauth/cb/google-analytics-4`
Google Ads (Campaign Management, Customer Match, Lead Forms, Reports)	`https://www.integromat.com/oauth/cb/google-ads2/` (Conversions: no trailing slash)
Google Search Console	`https://www.integromat.com/oauth/cb/google-serach-console` (spelled this way in Make's docs)
Google Business Profile (My Business)	Make's page lists two: `https://www.make.com/oauth/cb/google-my-business2` for the Google Business Profile connection type (Advanced settings) and `https://www.integromat.com/oauth/cb/google-custom` for the Google Custom Client Credentials connection type. Not sure which you'll use? Add both
Google Merchant Center	`https://www.integromat.com/oauth/cb/google-merchant`
Google Tasks · Google Photos · Google Keep	`…/oauth/cb/google-tasks` · `…/google-photos` · `…/google-keep` on `https://www.integromat.com`
Google Cloud Storage, Firestore, Text-to-Speech	`https://www.integromat.com/oauth/cb/google-custom`
Google Vertex AI	`https://www.make.com/oauth/cb/google-vertex-ai`
YouTube	`https://www.make.com/oauth/cb/youtube`
HTTP › Make a request calling a Google API	`https://www.integromat.com/oauth/cb/oauth2`

Copied from each app's "Create your client credentials" section on apps.make.com and from Make's Help Center, 3 October 2026. Some addresses have a trailing slash and some don't. Copy each one exactly as shown. We found no regional (eu1, us1 and so on) versions on any of the Google app pages we checked.

Also in Google Cloud: under Branding › Authorized domains, Make's docs say to add make.com and integromat.com.

Other popular apps

The same idea applies when an app lets you use your own client. Make's docs list these addresses:

Make app	Redirect or callback URL
Slack	User: `https://www.integromat.com/oauth/cb/slack2` · Bot: `https://www.integromat.com/oauth/cb/slack3`
Microsoft Teams	`https://www.integromat.com/oauth/cb/azure`
HubSpot CRM	`https://www.integromat.com/oauth/cb/hubspotcrm`
Salesforce	`https://www.integromat.com/oauth/cb/salesforce/`
Shopify	`https://www.integromat.com/oauth/cb/shopify/`
Facebook Pages, Instagram for Business	`https://www.integromat.com/oauth/cb/facebook`
LinkedIn · LinkedIn (OpenID Connect)	`https://www.integromat.com/oauth/cb/linkedin2` · `https://www.make.com/oauth/cb/linkedin-openid`
QuickBooks	Add both: `https://www.make.com/oauth/cb/quickbooks2` and `https://www.integromat.com/oauth/cb/quickbooks`
Notion	`https://www.integromat.com/oauth/cb/notion2`
Airtable	`https://www.integromat.com/oauth/cb/airtable3`
Pipedrive	`https://www.integromat.com/oauth/cb/pipedrive-auth`
Dropbox · Box · Zoom	`https://www.integromat.com/oauth/cb/dropbox/` · `…/box2` · `…/zoom2`
Mailchimp	`https://www.make.com/oauth/cb/mailchimp2`

From each app's page on apps.make.com, checked 3 October 2026. Not listed here? Open the app's page on apps.make.com and look for "Redirect URI" or "callback".

Create your own Google OAuth client for Make

These are the steps from Make's Help Center article "Connect to Google services using a custom OAuth client" (updated 2 October 2026). The app pages repeat them with each app's API, scopes and redirect URL.

Create a project in Google Cloud console. Make notes you need the serviceusage.services.enable permission.
Enable the API under APIs & Services › Library, for example the Google Drive API, Gmail API or Google Sheets API.
Configure the consent screen under APIs & Services › OAuth consent screen › Get Started. Set Audience to External for a personal account. Under Branding, add make.com and integromat.com as authorized domains.
Choose the publishing status under Audience: click Publish app (In production), or stay in Testing and add your Gmail address as a test user. Make: "If you keep your project in the Testing status, you will be required to reauthorize your connection in Make every week."
Add the scopes under Data Access › Add or remove scopes. For Google Sheets, Make lists …/auth/spreadsheets and …/auth/drive. For Gmail it lists gmail.modify, gmail.readonly, gmail.compose and gmail.send. Each app's page has its own list.
Create the client under Clients › + Create client. Choose Application type Web application, and under Authorized redirect URIs click + Add URI and paste the app's address from the table above. Copy the Client ID and Client secret.
Connect in Make. Add the Google module, click Create a connection, switch on Advanced settings, paste the Client ID and Client Secret, and click Sign in with Google.

"Needs verification" when you publish? Make's answer: "Currently, connecting to unverified apps works in Make, but we cannot guarantee that Google will allow connections to unverified apps for an indefinite period." Google lists "personal use" and "internal use within an organization" among the exceptions to restricted-scope verification (Google's restricted scope verification page, updated 19 August 2026). An unverified app shows Google's warning screen before sign-in, and Google caps such apps at "100 new users in total". That's fine for your own account, but not for a client you share widely.

Google lets you add more than one URI under Authorized redirect URIs. So in principle one client can serve several Make apps, for example google/ for Sheets and google-restricted for Drive, if it also has all their APIs and scopes. Make's docs describe one app at a time, so test each connection.

HTTP › Make a request with OAuth 2.0

Use this for any OAuth 2.0 API that Make has no app for, or for a Google API endpoint Make's modules don't cover. Make's docs (OAuth 2.0 authentication type, updated 22 December 2025) say to set the redirect URI in the other service's developer settings to https://www.integromat.com/oauth/cb/oauth2. Then:

In HTTP › Make a request, set Authentication type to OAuth 2.0 and click Create a connection.
Flow type: Authorization Code, which needs an Authorize URI and a Token URI, or Implicit, which needs only an Authorize URI. Both come from the service's API docs.
Add the Scopes, Client ID and Client Secret.
Under Advanced settings, pick the Scope separator, SPACE or COMMA. Make: "SPACE is the standard separator."

For Google APIs, Make's Help Center gives these values: Authorize URI https://accounts.google.com/o/oauth2/v2/auth, Token URI https://oauth2.googleapis.com/token, and Scope separator SPACE. Make warns: "Choosing the right scope separator is important, as the wrong one can prevent you from establishing the connection." To avoid having to keep refreshing the connection, add the Authorize parameters access_type = offline and prompt = consent. If Google says it hasn't verified the app, Make's article says to click Advanced, then "Go to integromat.com (unsafe)". The integromat.com name appears because of the redirect URL; it's Make's own domain.

Each HTTP request costs 1 credit, like any module run. Creating or reauthorizing a connection runs no module.

Custom apps: make.com/oauth/cb/app

If you're building your own app in Make's developer platform, a different set of callbacks applies. Make's developer docs say to use https://www.make.com/oauth/cb/app with the oauth.makeRedirectUri variable, or with oauth.localRedirectUri if you plan to request approval of your app. The old https://www.integromat.com/oauth/cb/app with oauth.redirectUri "is not suggested for new apps". For OAuth 1.0 custom apps the callback is https://www.integromat.com/oauth/cb/app-oauth1. Don't mix them up with oauth/cb/oauth2, which belongs to the HTTP app.

Errors while connecting, and the fixes

Error	What the source says	Fix
`Error 400: redirect_uri_mismatch`	Google: the redirect URI "must exactly match one of the authorized redirect URIs"; "the http or https scheme, case, and trailing slash ('/') must all match". Make: Google may not "instantly recognize" a new redirect URI.	Paste the app's exact address (table above), save, wait a while, then try again
`Error 401: invalid_client` ("The OAuth client was not found")	Make: the credentials "are no longer valid or properly configured". Google: `invalid_client` also means "The OAuth client secret is incorrect"	Re-copy the Client ID and secret; if the client is gone, create a new connection and swap it into your scenarios
`deleted_client`	Google: deleted manually "or automatically in the case of unused clients"; "Deleted clients can be restored within 30 days"	Restore it in Google Cloud, or create a new client and connection
`Error 403: access_denied`	Make: the project is in Testing and the Google account isn't added as a test user	Add the account as a test user, or publish the app; then click Reauthorize
`[403] Access Not Configured`	Make: the API isn't enabled in your project	Enable it under APIs & Services › Library
`Error 403: Insufficient Permission`	Make: required scopes are missing from the project	Add the app's scopes under Data Access, then Reauthorize
"It is not possible to use restricted scopes with customer @gmail.com accounts"	Make: the required scopes weren't added to your Google app	Add the scopes and finish the consent screen setup, then connect again
"Failed to verify connection 'My Google Restricted connection'. Status Code Error: 400"	Make: the connection "has expired and is no longer valid"; unpublished apps get "a 7-day authorization period"	Publish the app (In production) or reauthorize every week
"100 Logins Limit Per Day Has Been Reached"	Google: "a limit of 100 refresh tokens per Google Account per OAuth 2.0 client ID"; the oldest is invalidated "without warning"	Make suggests creating another OAuth client
HTTP OAuth 2.0 connection won't save	Make: check that the API is enabled, the authorized domains, the test user or published status, the redirect URI, the Authorize and Token URIs, the scopes, the Client ID and Secret, and the scope separator	For Google: SPACE separator, the two Google URIs above, and `oauth/cb/oauth2` as the redirect

Make: "Connect to Google services using a custom OAuth client" (Common problems) and "Call Google APIs with OAuth 2.0 HTTP request" (Troubleshooting), both updated 2 October 2026. Google: OAuth 2.0 for web server apps (updated 14 September 2026) and Using OAuth 2.0 (updated 26 May 2026).

Connection worked, then broke? For expired or revoked tokens (invalid_grant), weekly expiry in Testing status, "Access blocked" from a Workspace admin and the six-month Gmail limit, see Make Google connection errors. If a scenario switched itself off after the error, see scenario stopped or disabled. More error texts: Make error cheat sheet.

Own-project connections in other guides: YouTube automation covers the YouTube app's own-project connection and its publishing status. X (Twitter) automation explains why an HTTP OAuth 2.0 connection may not connect to X.

Plan check

Every plan, including Free: creating connections, using your own OAuth client, and the HTTP app. Make's docs for these connections don't mention a plan requirement. Free still means 1,000 credits a month, checks no more often than every 15 minutes, and 2 active scenarios.
Credits: connections themselves cost nothing. Each module run costs 1 credit, including each HTTP request.
Google side: Make's setup steps for the Google Cloud project and OAuth client don't include any billing step. Some Google APIs, such as Vertex AI, are billed by Google separately.
Not needed: the Make Code app (not on Free) or custom functions (Enterprise).

Make pricing page, as seen from a US connection, 3 October 2026. Plans change; check the current page before you buy.

Sources checked (3 October 2026)

Make app docs (apps.make.com): the redirect URIs and scopes in each app's "Create your client credentials" section for 37 Google apps and the other apps listed; Google Drive (custom client for @gmail), Gmail and Gmail (legacy); "Create and configure a Google Cloud Platform project for Gmail" (most updated 2 Oct 2026); OAuth 2.0 authentication type (updated 22 Dec 2025)
Make Help Center: "Connect to Google services using a custom OAuth client" and "Call Google APIs with OAuth 2.0 HTTP request" (both updated 2 Oct 2026); "Connect to any web service using OAuth 2.0"
Make developer docs: OAuth 2.0 and OAuth 1.0 connections for custom apps (callback URLs and IML variables)
Google for Developers: OAuth 2.0 for web server applications (redirect_uri rules, error codes; updated 14 Sep 2026); Using OAuth 2.0 (Testing status, 7-day refresh tokens, 100-token limit; updated 26 May 2026); restricted scope verification (updated 19 Aug 2026); Gmail API scopes (10 Sep 2026); Drive API scopes (3 Sep 2026); Sheets API scopes (3 Sep 2026)
Google Cloud Help: Restricted scopes; Unverified apps (unverified app screen, 100 new user cap)
Make pricing page: credit rule and Free plan limits, as seen from a US connection

Don't have a Make account yet? You can build and test this scenario on Make's free plan.

Create a free Make account (opens Make in a new tab)

Affiliate link: Flowpaja may earn a commission at no extra cost to you.

FAQ

What is Make's OAuth redirect URL?

It depends on the app. For HTTP › Make a request with OAuth 2.0 it's https://www.integromat.com/oauth/cb/oauth2. For Google Drive it's https://www.integromat.com/oauth/cb/google-restricted, for Google Sheets https://www.integromat.com/oauth/cb/google/ and for Gmail https://www.make.com/oauth/cb/google-email. Copy the exact address from the app's page in Make's docs.

Why do Make's redirect URLs still say integromat.com?

Make was called Integromat before it rebranded. Make's own documentation still lists integromat.com callback addresses for most apps, and tells you to add both make.com and integromat.com as authorized domains in Google Cloud.

What does google-restricted mean in the Make redirect URL?

It's the callback for Make's Google connection that covers restricted Google scopes, such as full Google Drive access. Google Drive, Gmail (legacy) and Google Groups use https://www.integromat.com/oauth/cb/google-restricted. Make's docs say personal @gmail.com accounts need their own OAuth client for Google Drive.

How do I fix Error 400: redirect_uri_mismatch in Make?

Add the app's exact redirect URL under Authorized redirect URIs in your Google OAuth client. Google says the scheme, case and trailing slash must all match. Save, wait a while (Make notes Google may not recognize a new URI instantly), then connect again.

Do I need my own Google OAuth client to use Make?

Usually not. Make's built-in connection works for most Google apps. You need your own client for Google Drive with a personal @gmail.com or @googlemail.com account, for HTTP › Make a request with OAuth 2.0, or if your organisation requires it.

Why does my custom Google connection expire every week?

Your Google Cloud project is in Testing status. Google issues refresh tokens that expire in 7 days for External apps in Testing. Publish the app under Google Auth Platform › Audience, then reauthorize the connection in Make.

Which redirect URL do Make custom apps use?

Make's developer docs recommend https://www.make.com/oauth/cb/app with the oauth.makeRedirectUri variable. The old https://www.integromat.com/oauth/cb/app is not suggested for new apps.

Make Google Sheets "Watch New Rows" not picking up new rows

Flowpaja — Sat, 17 Oct 2026 18:01:37 +0000

Short answer: Make's Google Sheets Watch New Rows trigger checks the sheet on the scenario's schedule and returns rows it hasn't processed yet. It misses rows when a blank row sits above them (Make's docs say rows after a blank row aren't processed), when it watches the wrong tab or header row, when its start point is past the new rows, or when rows are inserted, sorted or deleted. Remove blank rows, check the settings, reset Choose where to start, and add new rows only at the bottom.

Disclosure: everything in this guide works with plain Make.com and the apps it connects. At the end we mention our own Make templates and our Make scenario fix service on Fiverr. Module names, settings and limits were checked against Make's Google Sheets modules docs and types of modules in October 2026. Menus and limits change, so check them if something looks different.

What you need

The scenario with the Google Sheets → Watch New Rows trigger
Edit access to the sheet
A test row you can add and delete

How the trigger works (read this first)

Watch New Rows is a polling trigger: Google doesn't notify Make. Make checks the sheet on the scenario's schedule (e.g. every 15 minutes) and returns new rows, up to the Limit you set.

Make doesn't document how it remembers its place. In practice it behaves like a bookmark on row position, returning rows below the last one it processed, which fits Make's blank-row warning (step 2). It watches positions, not content, and most problems follow from that.

Step 1: Check the spreadsheet, tab and header row

Is the module pointing at the right spreadsheet (not an old copy) and the right Sheet Name (tab)? Re-linking a Google Form, for example, often creates a new tab such as "Form Responses 2".
Table contains headers: if Yes, the header row isn't returned as data, and the fields are named after the headers.
Row with headers: if your headers aren't in row 1, enter their range here, e.g. A3:F3.
The connected Google account must be able to open the file. A 403 or 404 here is an access problem, not a trigger problem: see Make.com Google connection errors.

Step 2: Remove blank rows

Make's documentation for Watch New Rows says: if a sheet contains a blank row, Make doesn't process the rows after it. One empty row in the middle of the data is enough to make every new row below it invisible.

Delete blank rows between the header and the data, and between data rows. Ask people who type into the sheet not to leave gaps.

Step 3: Reset "Choose where to start"

Right-click the trigger and click Choose where to start. The options vary by app. Make's help lists the typical ones: the current moment (From now on), a specific date, a specific record, or the first record (All). Your choice only applies to the first run after you save. Later runs continue from wherever the previous run stopped.

If the bookmark is past your new rows (e.g. after deleted rows were reused), the trigger skips them. Pick a start point just before the first unprocessed row, save, and click Run once.

Step 4: Inserting, sorting and deleting rows

Because the trigger follows row positions:

Inserting a row above the bookmark: that row is never picked up, and the rows below move down, so one of them can be processed twice.
Sorting the sheet causes the same problem on a larger scale.
Deleting rows: new rows can land on row numbers the trigger already counts as done.

Fix: treat the watched tab as an append-only log and sort on another tab, e.g. =SORT(Data!A2:F). If duplicates would hurt, store each processed row's unique ID in a data store and check it first.

Step 5: Rows added by formulas, forms and people

Formulas copied far down the sheet, or an ARRAYFORMULA that fills the whole column, can make rows look used before real data arrives. If the trigger returns bundles that contain only formula output, keep calculated columns on a separate tab, or only calculate where data exists, e.g. =IF(A2="","",…) (some locales use ; instead of ,). Then add a filter after the trigger: [key column] → Exists.
Rows added by other tools are fine if they're appended at the bottom, as Google Forms does.
Rows typed by hand can be picked up half-finished. Watch New Rows sees each row only once, so a "Ready" filter would skip that row for good. For hand-typed sheets, use Search Rows on a schedule with a Status column, as in the Gmail-on-new-row guide. If Search Rows then returns nothing, see Search Rows returns nothing.

Step 6: The schedule and the limit

With a 15-minute schedule, a new row can take up to 15 minutes to show up. That's expected.
Limit caps rows per run: 50 new rows with a limit of 2 take many runs.
Each check is one operation (one credit), even when nothing is new.
Check that the scenario is on. A scenario switched off after errors (see Errors before deactivation) picks up nothing. See why a Make scenario stopped running.

Step 7: When you need something instant

The Google Sheets Watch Changes module is instant, but it doesn't solve this. Make's docs say it only reacts to changes a person makes in Google Sheets, not to script or API edits, and it doesn't watch for newly added rows.

For rows that people add or edit, an installable Apps Script trigger can send the row to a Make custom webhook:

// Installable trigger: Extensions → Apps Script → Triggers → Add trigger
// → function sendRowToMake, event source "From spreadsheet", event type "On edit".
// Store the Make webhook URL in Script Properties as MAKE_WEBHOOK_URL.
function sendRowToMake(e) {
  const sheet = e.range.getSheet();
  if (sheet.getName() !== 'Data' || e.range.getRow() === 1) return;
  const row = sheet.getRange(e.range.getRow(), 1, 1, sheet.getLastColumn()).getValues()[0];
  const url = PropertiesService.getScriptProperties().getProperty('MAKE_WEBHOOK_URL');
  UrlFetchApp.fetch(url, {
    method: 'post',
    contentType: 'application/json',
    payload: JSON.stringify({ row: e.range.getRow(), values: row })
  });
}

Two limits: it fires on every edit, so filter in Make (e.g. only when "Ready" is TRUE). And Google's docs say script executions and API requests don't fire triggers, so rows written by other apps won't fire it. See receiving webhook data in Make.

If the rows come from Google Forms, start from the form instead: Make's Google Forms app has a Watch Responses trigger, and Apps Script has a separate "On form submit" trigger.

Common errors and fixes

Symptom	Likely cause	Fix
New rows never picked up	Blank row above them, wrong tab, or bookmark past them	Delete blank rows; check the tab; reset "Choose where to start"
Some rows skipped	Rows inserted above the bookmark, or the sheet was sorted	Append only; sort on another tab
Same row processed twice	Inserted or deleted rows shifted positions	Append-only tab + ID check
Empty bundles	Formulas filling the column	Limit formulas to filled rows; filter "Exists"
Half-filled rows processed	Picked up while someone was typing	Search Rows + Status column for hand-typed sheets
Nothing happens at all	Scenario switched off	Fix the error, switch it back on

Don't have a Make account yet? You can build and test this scenario on Make's free plan.

Create a free Make account (opens Make in a new tab)

Affiliate link: Flowpaja may earn a commission at no extra cost to you.

FAQ

Why doesn't Make's Watch New Rows see my new row?

It only runs on its schedule and only returns unprocessed rows. Check for blank rows above it, the tab and header settings, and the Choose where to start point.

Does a blank row stop Watch New Rows?

Yes. Make's documentation says that if a sheet contains a blank row, the rows after it aren't processed. Delete blank rows between your data.

Does Watch New Rows detect edits to existing rows?

No, only new rows. Watch Changes reacts to edits a person makes in Google Sheets, and an Apps Script on-edit trigger calling a Make webhook is another option.

Can I sort the sheet that Make is watching?

It's safer not to. Sorting moves rows to new positions, so rows can be skipped or processed twice. Sort on a separate tab.

How fast does Watch New Rows react?

As fast as the scenario's schedule. With a 15-minute interval, a row can wait up to 15 minutes, and each check uses one credit.

Why your Make.com scenario stopped running (and how to fix it)

Flowpaja — Fri, 16 Oct 2026 17:14:09 +0000

A scenario that worked for weeks goes quiet, and nobody notices until a client asks where their email is. Almost every case comes down to a short list of causes, and you can work through them in about fifteen minutes.

This guide contains affiliate links, marked “affiliate link”.

Disclosure: everything in this guide works with plain Make.com and the apps it connects. At the end we mention our own Make templates and our Make scenario fix service on Fiverr. Module names, settings and limits were checked against Make's scenario settings and error handling overview in October 2026. Menus and limits change, so check them if something looks different.

Short answer

Stored incomplete executions can block new runs when Process data in order is enabled. Check the scenario's current state and webhook queue. Resolve or deliberately handle the incomplete work, then test one new fictional request. Before enabling the scenario, inspect the destination using a fictional input and compare the result with the intended business outcome.

Key facts

Inspect incomplete executions before changing the trigger.
Turning scheduling on does not resolve incomplete work.
Do not discard stored data merely to make the queue look empty.

What you need

Access to the scenario in Make.com, with permission to edit it. No account yet? Create a free Make account (affiliate link).
Access to the organization's usage and connection pages
The notification emails Make sends to the account owner, if you still have them

Ad disclosure: links marked "affiliate link" are ads. If you sign up or buy through them, Flowpaja may earn a commission at no extra cost to you.

Step-by-step: find out why it stopped

1. Check the switch and the schedule

Open the scenario. Is the ON/OFF toggle on? Then look at the scheduling control at the bottom. If it is set to run on demand, or the schedule was switched off, the scenario will never start by itself. Cloned or imported scenarios often arrive inactive or with scheduling turned off, so a "new" copy that never runs is a common case.

2. Open the History tab

Each run is listed with a status. Look for the last successful run and the first failure after it. Click the failed run and find the module with the red marker. The error message there is usually the whole answer. If there are no runs at all after a certain time, the cause is not an error in a module: look at scheduling, deactivation or credits.

3. Check whether Make disabled the scenario

Make switches a scenario off when it ends with an error several runs in a row. You set the number in the scenario settings ("Errors before deactivation"), and Make's help center gives 3 as the default. Some cases skip the count: a scenario that starts with an instant trigger, such as a webhook, is deactivated after the first error, and fatal errors such as AccountValidationError, OperationsLimitExceededError and DataSizeLimitExceededError switch off scheduling immediately. Runs that end with a warning do not count. The account owner normally gets an email when it happens. Fix the cause of the error first, then switch the scenario on. If you only switch it on, it will fail and stop again.

4. Look at incomplete executions

Open the Incomplete executions tab of the scenario. Runs that failed while Store incomplete executions is enabled in the scenario settings, or that hit a Retry error handler (called Break in older versions), wait here. Stored incomplete executions count toward your plan's storage. You can open each one, see the error, fix the problem and retry or delete it. This matters for two reasons: unresolved items can pile up unnoticed, and if Process data in order (sequential processing) is enabled, Make pauses new runs until all incomplete executions are resolved. If new data arrives but nothing is processed, check this tab.

Statuses, automatic retries and manual resolve: Make incomplete executions.

5. Check the connections

Go to the Connections page in Make and look for a warning on any connection used in the scenario. Google connections expire when you change your Google password, when access is revoked, or when you use your own Google OAuth app that is still in "Testing" status (Google can expire those tokens after about a week). Reauthorize the connection, then run the scenario once manually. For every Google-specific cause and fix, see Make.com Google connection errors.

6. Check credits

Make counts usage in credits (older plans and docs say operations). On the organization's dashboard or usage page you can see how much of the monthly allowance is used. When credits run out, modules fail with OperationsLimitExceededError and Make switches off the scenario's scheduling straight away. After the allowance renews or you buy extra credits, check that the scenario is switched on again. If it ran out early, open the History of your busiest scenarios and look for one that runs every minute on a trigger that rarely has data. What uses credits and how to use fewer: Make credits explained.

7. Check data store limits

Open the Data stores page. Each store has a size, and your plan has a total storage limit. When it is full, writes fail with an error, and that can trigger the consecutive-error shutdown from step 3. Delete old records, add a cleanup step that removes records past a certain age, or raise your storage allowance.

8. Add alerts so you find out first

For important scenarios, add an error handler route on the risky module that sends you an email or a Slack message with the scenario name and the error text. A silent failure is the expensive kind.

Free cheat sheet

Which errors switch a scenario off straight away? The free Make Error Cheat Sheet marks every error type that deactivates a scenario immediately, plus the first fix for each. Two printable pages.

Open the cheat sheet
Download the PDF

Common errors and fixes

"Token has been expired or revoked" or a 401 from Google. The connection lost its authorization. Reauthorize it in Connections. If it keeps happening every week, you are probably on a custom Google app in Testing status, so publish the app or use the default Make connection if your use case allows it.

OperationsLimitExceededError: the credit limit is reached. Make treats this as a fatal error and switches off scheduling right away, without waiting for the consecutive-error count. Buy extra credits, upgrade or wait for renewal, then switch the scenario back on. Also find the scenario that used them up: a schedule of every minute on a Watch trigger that finds nothing still uses a credit on every check. Lowering the frequency is often enough.

A data store error mentioning storage or size. The store or your total storage is full. Delete records first, then enable the scenario. Check the current limits for your plan.

The scenario switched itself off after repeated errors. One failing module, often a connection or a changed field in the source sheet, produced several errors in a row. The consecutive-errors setting did what it is meant to do. Fix the cause, run once manually and confirm success before enabling it.

New data arrives but nothing runs, and there are no errors. Check incomplete executions if Process data in order is enabled, and check that the webhook or trigger still points at the active scenario. A scenario that was duplicated may have a new webhook URL.

Runs time out or end with "scenario execution time exceeded". A single run took longer than the limit for your plan. Lower the number of items processed per run, or split the work across two scenarios. Make's pricing table lists 40 minutes on paid plans and 5 on the Free plan (checked 3 October 2026; Make's Help Center errors page says 45 and 10), and the interrupted run doesn't store an incomplete execution. Every limit and its fix: Make timeouts and limits.

"Scenario was rejected: scenario is running." Make's help center doesn't document this exact message. As worded, it says Make didn't start a new run because this scenario was already running. Open the scenario and wait for the current run to finish, or click Stop (Make lets the module that is working finish its bundles, then stops the run), and start it again. Make interrupts any run after 40 minutes on paid plans (5 minutes on the Free plan), so if the message still appears after that, contact Make support.

Quick reference: Make error cheat sheet, every common error type, HTTP code and app error on one page, with a free printable PDF.

Don't have a Make account yet? You can build and test this scenario on Make's free plan.

Create a free Make account (opens Make in a new tab)

Affiliate link: Flowpaja may earn a commission at no extra cost to you.

FAQ

Does Make tell me when a scenario is disabled?

Usually by email to the account owner, and in the scenario list. Check notification settings in your profile and organization so the email goes to someone who reads it.

Will I lose the data from the runs that failed?

Not necessarily. If incomplete executions were stored, you can retry them after fixing the cause. If storing was off, the data from a failed run is gone, though your source system may still hold it.

Can I stop a scenario from being disabled?

You can change the consecutive-errors setting, but a higher number only delays the shutdown, and it does not apply to instant triggers or fatal errors. Handling the error properly, with Retry, Skip or a notification route, is better than raising the limit.

Is there a difference between "inactive" and "paused"?

The labels can change between interface versions. Look at the toggle and the schedule, and use the History tab to confirm whether runs are happening.

What should I save before re-enabling a stopped scenario?

Save the last relevant run, failing module, input identity and error details. Inspect whether any destination actions already succeeded before the stop. Fix the earliest known cause and use a controlled input to confirm the intended result. Enabling the scenario again without this evidence can repeat the same failure or duplicate an action that already completed.

How do I test a repaired instant-trigger scenario before returning it to service?

Use a fictional payload that exercises the repaired boundary and inspect the final destination. Confirm the trigger is listening at the intended URL and that recovery behavior is deliberate. An instant-trigger scenario can deactivate after its first unhandled error, so inspect the run result and activation state before returning the operational sender to the workflow.

Make.com webhook not receiving data: how to fix it

Flowpaja — Fri, 16 Oct 2026 17:13:56 +0000

Short answer: When a Make.com custom webhook doesn't receive data, the sender is usually calling a different URL, the scenario is off, or Make is rejecting the request. Check the URL first, then open the webhook's Queue and Logs tabs to see whether requests arrive at all. A test request with curl.exe shows which side the problem is on.

This guide contains affiliate links, marked “affiliate link”.

Disclosure: everything in this guide works with plain Make.com and the apps it connects. At the end we mention our own Make templates and our Make scenario fix service on Fiverr. Module names, settings and limits were checked against Make's webhooks docs and Webhooks app docs in October 2026. Menus and limits change, so check them if something looks different.

What you need

Access to the scenario in Make.com and to Webhooks in the left sidebar. No account yet? Create a free Make account (affiliate link).
Access to the sending app's webhook settings, and its delivery log if it has one
On Windows: Command Prompt (cmd). Windows 10 and 11 include curl.exe.

Ad disclosure: links marked "affiliate link" are ads. If you sign up or buy through them, Flowpaja may earn a commission at no extra cost to you.

Step 1: Check the URL, character by character

Most "not receiving" cases are a URL mismatch:

Copy errors. A missing last character, a trailing space, or a pasted line break.
A different webhook. Each scenario uses its own webhook. If you cloned or imported the scenario, or added a new webhook to the trigger, the URL changed, and the sender may still call the old one.
The zone. URLs include your zone, e.g. https://hook.eu1.make.com/… or https://hook.us1.make.com/…. Never retype or edit the URL.

Copy the URL from the Custom webhook module and paste it into the sender again rather than comparing by eye.

Step 2: Check that the scenario is on, and how it's scheduled

Check that the scenario is active and set to run Immediately (the default for webhooks). On a schedule, requests wait in the queue, and each run processes only up to the webhook's Maximum number of results (default 2).

Also check whether Make switched the scenario off. If a run of a webhook-triggered scenario set to run immediately ends in an error, Make deactivates it at once; Errors before deactivation (default 3) doesn't apply. See why a Make scenario stopped running.

Step 3: Look at the webhook queue

In the left sidebar, click Webhooks, select your webhook and open the Queue tab. Click Detail on an item to see its parsed data.

Items waiting, nothing running: requests reach Make, but the scenario is off, scheduled, or has Process data in order on and is waiting for an unresolved incomplete execution.
Queue empty: requests aren't arriving, or Make rejected them. Continue with step 4.

The queue holds 667 items per 10,000 monthly credits in your plan, up to 10,000. When it's full, Make answers 400 with Queue is full.

Step 4: Check the webhook logs

On the same page, open the Logs tab. Detail shows the full request (method, headers, query, body), Make's response status and the parsed items. Logs are kept for 3 days (30 on Enterprise).

Request in the logs: compare the status and parsed items with what you expected (steps 5 and 8).
Nothing in the logs: the request never reached this webhook. Recheck step 1 and the sender's delivery log.

Step 5: Check the webhook's settings

On the Webhooks page, open the webhook's three-dot menu → Edit. These settings can block or reshape requests:

API Key authentication: the sender must send a key in the x-make-apikey header.
IP restrictions: only listed IPs are processed.
Data structure: requests that fail validation get 400.
JSON pass-through: the JSON body arrives as one text string, not separate fields. Switch it off, or parse the text with Parse JSON.

Payloads can be up to 5 MB. Above 300 requests per 10 seconds, Make answers 429.

Step 6: Let Make learn the data structure

A new webhook doesn't know which fields to expect. Click Run once so the module listens, send one realistic request (step 7), and check that the fields appear in its output.

If the sender later adds or renames fields, click Detect new values in the module and send a new sample. Otherwise the new fields don't show up in the mapping panel.

Step 7: Send a test request with curl.exe

If your own request arrives and the sender's don't, the problem is on the sender's side. A test runs the scenario like a real request, so use test data.

Quickest check: paste the URL into a browser; a working webhook shows Accepted. For a JSON POST, run this in Command Prompt (one line):

curl.exe -X POST "https://hook.eu1.make.com/YOUR-WEBHOOK-ID" -H "Content-Type: application/json" -d "{\"name\":\"Test User\",\"email\":\"test@example.com\"}"

In cmd, wrap the JSON in double quotes and write inner quotes as \". Expect Accepted (status 200) unless your scenario has a Webhook response module.

PowerShell note: in Windows PowerShell 5.1, curl is an alias for Invoke-WebRequest, which takes different parameters. curl.exe calls the real curl, but PowerShell quotes differently, so the line above fails there unchanged. Use PowerShell's own command:

$body = @{ name = "Test User"; email = "test@example.com" } | ConvertTo-Json
Invoke-RestMethod -Method Post -Uri "https://hook.eu1.make.com/YOUR-WEBHOOK-ID" -ContentType "application/json" -Body $body

On macOS or Linux: curl -X POST "URL" -H "Content-Type: application/json" -d '{"name":"Test User"}'.

Step 8: Check what the sender actually sends

Content type. Make documents query strings, form data (application/x-www-form-urlencoded, multipart/form-data) and JSON with Content-Type: application/json. For anything else, compare the body and parsed items in the Logs tab.
Different format from your test. If the sender posts form data but you taught Make with JSON, fields differ. Use Detect new values with a real request.
Method. Some tools send GET; the data is then in the query string.
Events. If the event you expect isn't ticked in the sender's webhook settings, nothing is sent.
Sender errors. Check the sender's delivery log for timeouts or error responses.

Step 9: Check for a deactivated webhook

Make deactivates a webhook that isn't connected to any scenario for more than 5 days (120 hours); its URL then answers 410 Gone. This typically follows a deleted or rebuilt scenario. Check the status on the Webhooks page; if it's deactivated, create a new webhook and give the sender the new URL.

Common errors and fixes

For errors outside webhooks, see 10 common Make scenario errors.

What you see	Likely cause	Fix
Module waiting for data	No request reached that URL	Test (step 7); recheck the URL
`410 Gone`	No scenario attached for over 5 days	New webhook; update the sender
`400 Queue is full`	Queue limit reached	Process or delete queued items
`400`, data structure attached	Failed validation	Fix the payload or structure
`429`	Over 300 requests in 10 seconds	Slow down the sender
Queue fills, nothing runs	Scenario off, scheduled or waiting	Fix and switch on
Fields missing in mapping	Outdated structure	Detect new values
`curl` fails in PowerShell	Alias for Invoke-WebRequest	Invoke-RestMethod, or `cmd`
One text value, no fields	JSON pass-through or content type	Turn it off / send JSON

New to webhooks? Start with the Make webhook tutorial, or read Make.com for beginners for the basics.

Requests arriving twice? Our free Webhook to Google Sheets with duplicate check template adds one row per request_id and skips repeats.

Quick reference: Make error cheat sheet, every common error type, HTTP code and app error on one page, with a free printable PDF.

Building the webhook from scratch? See receive webhook data in Google Sheets. Building form → Slack instead? See Google Form responses to Slack or the free Form to Slack template.

Don't have a Make account yet? You can build and test this scenario on Make's free plan.

Create a free Make account (opens Make in a new tab)

Affiliate link: Flowpaja may earn a commission at no extra cost to you.

FAQ

Why does my Make webhook say it's waiting for data?

No request has reached that exact URL since you clicked Run once. Send a test with curl.exe or trigger the sending app, and check the URL.

Does a Make webhook receive data while the scenario is off?

Yes. Requests wait in the webhook's queue, up to its limit, but don't run the scenario while it's off. Check the Queue tab before switching it back on.

Why doesn't curl work in PowerShell?

In Windows PowerShell 5.1, curl is an alias for Invoke-WebRequest, which uses different parameters. Use Invoke-RestMethod, or run curl.exe from Command Prompt.

Do I need to update the data structure after changing the form?

Yes, if fields were added or renamed. Click Detect new values in the Custom webhook module and send a new sample.

Why did my webhook stop working after a few days?

Make deactivates a webhook that isn't connected to any scenario for more than 5 days (410 Gone), or an error switched the scenario off. Check the webhook's status and the scenario's History.

20 Make.com automation examples for small businesses

Flowpaja — Fri, 16 Oct 2026 11:16:28 +0000

Short answer: The Make automations that pay off first in a small business are the boring ones. Send form leads to your CRM and Slack, chase unpaid invoices, draft quote follow-ups, log orders to a sheet, file email attachments and send a daily summary. Below are 20 examples Make can run today. Each one names the trigger and modules, gives a rough credit count per run and links to a step-by-step Flowpaja guide or a ready-made template, so you can build it rather than just read about it. Most run on Make's Free plan at low volume.

This guide contains affiliate links, marked “affiliate link”.

All 20 examples at a glance

Difficulty is our rough rating: Easy means 2–3 modules and no data juggling, Medium adds a search, router or duplicate check, and Advanced involves an extra account setup, AI or several linked records. "Check" means a scheduled trigger run, which uses a credit even when nothing is new.

#	Example	Apps	Difficulty	Est. credits per run	Build it
1	New form response → Slack message	Google Forms/Sheets, Slack	Easy	1 per check + 1 per response	Free template
2	Form lead → HubSpot contact + hot-lead Slack alert	Sheets or Tally or Typeform, HubSpot, Slack	Medium	About 3 per lead (+1 per check)	Guide
3	Form lead → Pipedrive lead without duplicate people	Sheets or form app, Pipedrive	Medium	4–5 per lead	Guide
4	Typeform or Tally response → Google Sheets row	Typeform or Tally, Sheets	Easy	About 3 per response	Guide
5	Facebook lead ad → sheet row + email	Facebook Lead Ads, Sheets, Gmail	Medium	3–4 per lead	Guide
6	Polite invoice payment reminders	Sheets, Gmail	Medium	1 per run + 2–3 per reminder	Guide
7	Daily overdue-invoice digest to yourself	Sheets, Gmail	Easy	1–2 per day, about 4 with overdue invoices	Free template
8	Create invoices and record payments in QuickBooks or Xero	Sheets, QuickBooks or Xero	Advanced	About 6–8 per invoice	Guide
9	Quote follow-up drafts after 7 days	Sheets, Gmail	Easy	1–2 per run + 2–4 per follow-up	Free template
10	Send an email when a row is ready	Sheets, Gmail	Easy	1 per run + about 3 per email	Guide
11	Shopify order → sheet row + Slack alert	Shopify, Sheets, Slack	Medium	About 4 per order, more per line item	Guide
12	WhatsApp order confirmations	Sheets, WhatsApp Business Cloud	Advanced	1 per check + 2 per order	Guide
13	Save Gmail attachments to Google Drive folders	Gmail, Google Drive	Medium	1 per check + about 4–5 per email + 1 per file	Guide
14	Webhook data → sheet, without duplicate rows	Webhooks, Sheets	Easy	About 3 per new row	Free template
15	Booking form → Google Calendar event	Forms/Sheets, Google Calendar	Medium	About 5–6 per response (+1 per check)	Guide
16	Daily summary email from a sheet	Sheets, Gmail	Easy	About 3 per day	Guide
17	Form or payment alerts in Discord	Webhooks or Stripe, Discord	Easy	2 per submission	Guide
18	Sort incoming email with AI labels	Gmail, OpenAI (or Claude/Gemini)	Medium	1 per check + 2 per email, plus the AI provider's token bill	Guide
19	Support-email triage with a Make AI agent	Gmail, Make AI Agent, Sheets, Slack	Advanced	Varies with tokens and tools used	Guide
20	Ask Claude who owes you money (MCP)	Make MCP server, Sheets	Advanced	About 2–3 per question	Guide

Credits are our estimates for one run, counted at about 1 credit per module action. Routers, filters and error handlers use none. Check the real count in your scenario's History.

Start with the existing setup reference Start with this live narrow pattern and read its own setup, test scope and limits before adapting it.

Open the free reference

How we count the credits

Make bills in credits. Make's pricing page says each module action uses credits, whether it reads, searches, creates, updates, transforms, aggregates or iterates data, and that routers and error handlers don't. Filters aren't modules, so they're free too. For the standard modules in these examples that works out at about 1 credit per module, per bundle (item) it processes. Two things push the number up:

Scheduled triggers. A "Watch" or "Search Rows" trigger on a schedule uses a credit on every check, even when nothing is new. Checking every 15 minutes is up to 96 checks a day, which is about 2,900 a month on its own. An instant trigger (a webhook, Tally, Typeform, Facebook Lead Ads New Lead, Shopify Watch events) runs only when data arrives.
Many items per run. If a search returns 10 rows, every module after it runs 10 times. Our Make credits guide shows how to estimate a month, and the Make credits calculator does the sum for you.

AI modules can add token-based credits on top, depending on how you connect them. Each example below says how.

Sales and leads

Lead handling is where most small businesses start: a form fills up, and someone has to copy the details into a CRM, tell the team and reply. Make does all three in one scenario.

1. New form response → Slack message

Post every Google Form response to a Slack channel, so nobody has to keep the response sheet open.

Who it's for: any team that takes enquiries, bookings or internal requests through Google Forms and talks in Slack.
Trigger → modules: Google Sheets Watch New Rows on the form's response sheet → Slack Send a Message.
Credits: 1 per scheduled check (even with no new responses) + 1 per response posted.
Plan fit: Free. On Free, check hourly rather than every 15 minutes so the checks don't eat your 1,000 credits.
What usually breaks: the trigger runs but finds nothing, because it starts "from now on" (Watch Rows not triggering), or Slack answers channel_not_found (fix it here).
Build it: free Form responses to Slack template · step-by-step guide

2. Form lead → HubSpot contact + hot-lead Slack alert

Create or update the contact in HubSpot and ping Slack only when the lead looks hot, for example a large budget.

Who it's for: service businesses using HubSpot's free CRM.
Trigger → modules: Google Sheets Watch New Rows → HubSpot CRM Search for Contacts (by email) → Router → Create a Contact or Update a Contact → Router (hot lead?) → Slack Send a Message. With Tally, use Tally Watch New Responses → HubSpot CRM Create or Update a Contact instead.
Credits: about 3 per lead (search, create or update, Slack) + 1 per scheduled check. The Tally version is instant: about 3 per submission, with nothing spent on empty checks.
Plan fit: Free at low volume. If you use Typeform, its native HubSpot integration may be enough without Make; the Typeform to HubSpot guide explains when to use which.
What usually breaks: a plain "create" fails when someone submits twice, because HubSpot rejects a second contact with the same email. Dropdown properties also need HubSpot's internal value, not the visible label.
Build it: Google Forms to HubSpot and Slack · Tally to HubSpot · Lead Router template ($19)

3. Form lead → Pipedrive lead without duplicate people

Pipedrive's own automations only react to records already inside Pipedrive, so leads from a Google Form or website form need an outside tool.

Who it's for: small sales teams on Pipedrive.
Trigger → modules: your form trigger → Pipedrive Search Persons (by email) → Create a Person (only if none found) → Create a Lead → Create a Note with the answers.
Credits: 4 per lead for a known person, 5 for a new one.
Plan fit: Free at low volume.
What usually breaks: two submissions seconds apart can both create the person. Turn on Process data in order in the scenario settings, so each run finishes before the next starts.
Build it: Pipedrive and Make guide

4. Typeform or Tally response → Google Sheets row

Keep one clean sheet of every response, ready for reports or the next automation.

Who it's for: anyone collecting enquiries, orders or applications in Typeform or Tally.
Trigger → modules: Typeform Watch Responses or Tally Watch New Responses (use Typeform's instant version; Tally's is instant) → Google Sheets Search Rows (by response ID) → Router → Add a Row only if it's new.
Credits: about 3 per response (trigger, search, add).
Plan fit: Free. At 3 credits a response, 1,000 credits cover roughly 330 responses a month if nothing else uses them.
What usually breaks: a new question doesn't appear in the mapping panel until Make sees a fresh response, and multiple-choice answers show as [object Object] until you map the label. If nothing arrives at all, see webhook not receiving data.
Build it: Tally to Google Sheets · Typeform to Google Sheets · Typeform to Sheets, Slack and Gmail

5. Facebook lead ad → sheet row + email

Get leads out of Meta's Lead Ads into a sheet and in front of you while they're still warm.

Who it's for: local businesses running Facebook or Instagram lead ads.
Trigger → modules: Facebook Lead Ads New Lead (instant) → Google Sheets Search Rows (lead ID, optional duplicate check) → Add a Row → Gmail Send an email to you, or Create a draft email to the lead for review.
Credits: about 3 per lead, or 4 with the duplicate check.
Plan fit: Free at low volume.
What usually breaks: New Lead never fires because Make lacks Leads Access, the Page isn't ticked in Business Integrations, or the app isn't subscribed to the Page.
Build it: Instagram and Facebook automation guide

Invoices and getting paid

These keep money coming in without you rereading the invoice list every morning. All three start from a Google Sheet, so you can keep invoicing the way you do now.

6. Polite invoice payment reminders

Email clients a friendly reminder a few days after the due date, then a firmer one and a final one, and record what was sent.

Who it's for: freelancers and small firms that track invoices in a sheet.
Trigger → modules: daily schedule → Google Sheets Search Rows (unpaid) → filter (reminder due, fewer than three sent) → Update a Row (reminder count, date, recorded before sending) → Router (which reminder?) → Gmail Send an email.
Credits: 1 per daily run + 2 per reminder (3 if you also log each email).
Plan fit: Free. A daily run is about 30 credits a month plus the reminders.
What usually breaks: dates arrive as text in another format, so the "due" filter never passes (date errors in Make). It also can't know a client paid until you mark the row.
Build it: step-by-step guide · Polite Invoice Reminder template ($19)

7. Daily overdue-invoice digest to yourself

One email each morning listing what's overdue, sent only to you. Nothing goes to clients, which makes it a safe first scenario.

Who it's for: owners who want a nudge before they chase anyone.
Trigger → modules: daily schedule → Google Sheets Search Rows (overdue) → Tools Text aggregator → JSON Parse JSON (list and totals) → Gmail Send an email, the four modules of the free template.
Credits: about 4 on days with overdue invoices, 1–2 on other days, so roughly 30–120 a month.
Plan fit: Free.
What usually breaks: Search Rows returns nothing because of a filter or header mismatch (Search Rows empty).
Build it: free Overdue Invoice Digest template · step-by-step guide. No Make at all? Highlight overdue invoices with Sheets formulas.

8. Create invoices and record payments in QuickBooks or Xero

Turn rows in a sheet (or Stripe payments) into invoices in your accounting tool, and write the paid status back.

Who it's for: businesses that already use QuickBooks Online or Xero.
Trigger → modules: Google Sheets Search Rows → QuickBooks Search for Customers or Xero Search for Contacts → Create a Customer / Create a Contact if missing → Create an Invoice. For payments: Create a Payment, then update the sheet. Stripe Watch Events can start it instead.
Credits: about 6–8 per invoice in our worked example, including the aggregator that checks the search result.
Plan fit: Free to test. Check what your accounting plan allows through its API.
What usually breaks: a new customer is created every time, because a router after a zero-result search never takes the "found" route. The fix is an aggregator and a length() check (Iterator vs Aggregator).
Build it: QuickBooks and Xero invoices guide

Quotes and follow-ups

9. Quote follow-up drafts after 7 days

Find quotes that have had no answer for a week and put a follow-up draft in your Gmail. You read and send it yourself.

Who it's for: trades, agencies and consultants who send quotes and forget to chase them.
Trigger → modules: daily schedule → Google Sheets Search Rows (sent, no reply, 7+ days) → Gmail Create a draft email → Update a Row (follow-up drafted).
Credits: the free template uses 1 per run + 2 per draft (roughly 30–60 a month). The fuller guide build uses 2 per run + about 4 per follow-up.
Plan fit: Free.
What usually breaks: Update a Row fails without a row number (missing row number). Personal Gmail connections also need re-authorizing about every six months, according to Make's Gmail docs.
Build it: free One quote follow-up draft template · step-by-step guide · Quote Follow-Up Assistant ($19)

10. Send an email when a row is ready

Send a welcome, confirmation or "your order is ready" email when a row reaches a certain status, exactly once.

Who it's for: anyone running a process from a shared sheet.
Trigger → modules: schedule → Google Sheets Search Rows (ready, not yet emailed) → Update a Row (mark "sending") → Gmail Send an email → Update a Row (sent). Watch New Rows also works for brand-new rows.
Credits: 1 per run + about 3 per email, counted from the modules.
Plan fit: Free.
What usually breaks: Gmail returns "Invalid to header" when the cell has a trailing space, a line break or two addresses. Wrapping the field in trim() fixes most cases.
Build it: Gmail email for a new row guide

Orders and customers

11. Shopify order → sheet row + Slack alert

Log every order to a sheet for reporting or fulfilment and tell the team in Slack.

Who it's for: small Shopify stores.
Trigger → modules: Shopify Watch events (instant) or Watch orders (scheduled) → Google Sheets Search Rows (order ID) → Add a Row → Slack Send a Message. For one row per product, add an Iterator; for large orders, an Array aggregator and Bulk Add Rows (Advanced) write once per order.
Credits: about 4 per order with the instant trigger, counted from the modules. One row per line item adds credits per item, and the scheduled trigger adds 1 per check.
Plan fit: Free for a quiet store. Check your volume with the credits calculator.
What usually breaks: duplicate rows from webhook retries or re-runs. Search before you add, and remember that an empty search still passes one empty bundle on.
Build it: Shopify orders to Google Sheets guide

12. WhatsApp order confirmations

When an order is marked confirmed in your sheet, send the customer an approved WhatsApp template message.

Who it's for: shops and service businesses whose customers prefer WhatsApp.
Trigger → modules: schedule → Google Sheets Search Rows (confirmed, not yet sent) → filter → WhatsApp Business Cloud Send a Template Message → Update a Row.
Credits: 1 per check + 2 per order, so an hourly check that finds 3 orders uses 7.
Plan fit: Make's Free plan is enough to test. You also need a Meta business setup and approved message templates, and Meta may charge for messages, so check Meta's current pricing.
What usually breaks: the module shows success but nothing arrives. Usually it's a free-form message outside the 24-hour window, a free tier used up with no payment method, or a recipient who hasn't opted in.
Build it: WhatsApp automation guide

Admin and back office

13. Save Gmail attachments to Google Drive folders

File invoices, receipts and supplier documents from email into one Drive folder per month, automatically.

Who it's for: anyone whose bookkeeper asks for "all the receipts" every month.
Trigger → modules: Gmail Watch emails (filter by sender, label or "has attachment" in the trigger) → Google Drive Search for Files/Folders (month folder) → Array aggregator → Router → Create a Folder if missing → Search for Files/Folders again (folder ID) → Iterator over the attachments → filter (skip signature images) → Upload a File.
Credits: 1 per scheduled check, then about 4 per email (two folder searches, the aggregator and the Iterator), 5 when it creates the month's folder, plus 1 per uploaded file. Counted from the modules. Emails filtered out in the trigger cost nothing further.
Plan fit: Free for small volumes. The Free plan's 5 MB file size limit can block larger attachments; paid plans allow bigger files (make.com/en/pricing).
What usually breaks: files upload but won't open, or are 0 bytes, because the Data field is mapped to the whole attachments array instead of the current item (Iterator vs Aggregator). Signature images also pile up unless you filter by file type.
Build it: Gmail attachments to Google Drive guide. To read the saved PDFs or create your own: PDF automation in Make.

14. Webhook data → sheet, without duplicate rows

Catch data from your website, a booking tool or any app that can send a webhook, and add it to a sheet once, even when the sender retries.

Who it's for: anyone whose tool has a "webhook" setting but no Make app.
Trigger → modules: Webhooks Custom webhook (instant) → Google Sheets Search Rows (by ID) → filter → Add a Row. Add a Webhook response only if your sender expects a specific reply (one more credit).
Credits: 3 per new row and 2 per skipped duplicate, measured in our template test. No requests means no credits.
Plan fit: Free. The template uses no paid-only features.
What usually breaks: fields don't appear in the mapping panel because Make learned the structure from an empty request. Click Detect new values in the Custom webhook module and send a full sample. If requests never arrive, see webhook not receiving data.
Build it: free Webhook to Sheets with duplicate check template · step-by-step guide

15. Booking form → Google Calendar event

Turn a booking or appointment request into a calendar event at the right time, in the right time zone.

Who it's for: consultants, trainers and service businesses that take bookings through a Google Form.
Trigger → modules: Google Sheets Watch New Rows on the response sheet (or Google Forms Watch Responses) → three Tools Set variable modules (combine date and time, parse it in your time zone, work out the end time) → Google Calendar Search Events → Router → Create an Event → optional Google Sheets Update a Row.
Credits: about 5–6 per response (three variables, the search and the event, plus Update a Row if you use it), counted from the modules, plus 1 per check for the scheduled trigger.
Plan fit: Free.
What usually breaks: the event lands an hour or more off because the date was parsed without a time zone (date errors in Make).
Build it: Google Forms to Google Calendar guide

16. Daily summary email from a sheet

A morning email with today's jobs, new leads or open tasks as a small table.

Who it's for: owners and team leads who live in a shared sheet.
Trigger → modules: daily schedule → Google Sheets Search Rows → Tools Text aggregator (builds the table) → Gmail Send an email.
Credits: about 3 per day, counted from the modules.
Plan fit: Free.
What usually breaks: the email shows raw HTML tags (set the Gmail body type to Raw HTML), or an ampersand or line break in a cell breaks the table. escapeHTML() fixes most of that.
Build it: daily summary email guide

Team alerts

17. Form or payment alerts in Discord

Post new form submissions or Stripe payments to a Discord channel as a tidy embed.

Who it's for: small teams and communities that work in Discord rather than Slack.
Trigger → modules: Webhooks Custom webhook or Stripe Watch Events → HTTP Make a request to a Discord webhook URL with an embed. Make's Discord app works too.
Credits: 2 per submission (webhook + HTTP).
Plan fit: Free.
What usually breaks: quotes or line breaks in mapped text break the JSON string, so Discord rejects the request. The Make error cheat sheet lists the common 400 errors.
Build it: Discord automation guide

AI examples

AI steps are the newest part of Make and change fastest. Keep a human check wherever a wrong answer would reach a customer.

18. Sort incoming email with AI labels

Have an AI model read each new email and label it, for example quote request, invoice, support or spam, so your inbox sorts itself.

Who it's for: owners whose one inbox gets everything.
Trigger → modules: Gmail Watch emails → OpenAI Transform text to structured data (returns the category) → Gmail Update email labels. The Anthropic Claude and Google Gemini AI apps work the same way.
Credits: 1 per check + 2 per email (AI module + label). With your own API key, OpenAI bills the tokens separately. Claude's and Gemini's no-key Simple Text Prompt modules bill tokens in Make credits instead.
Plan fit: Free to build and test.
What usually breaks: a 401 error from a wrong or revoked API key, or a 429 rate limit. Add an error route so one failed email doesn't stop the run (Make error handling).
Build it: ChatGPT and OpenAI in Make · Claude and Gemini in Make

19. Support-email triage with a Make AI agent

An agent reads each support email, looks up the order, logs the request and alerts the team. It decides which tools to use rather than following fixed routes.

Who it's for: small shops and SaaS teams that already have the fixed-route basics running.
Trigger → modules: Gmail Watch emails → Make AI Agent (New) Run an agent, with tools: a "Find order" scenario (Search Rows → Router → Return output, scheduled On demand), Google Sheets Add a Row and Slack Send a Message.
Credits: varies. The agent uses credits per operation plus token-based credits when you use Make's AI Provider, and each tool it calls uses its own credits. Run a few test emails and read the History.
Plan fit: Make's pricing table lists AI Agents (beta) on every plan, including Free, with Make's AI Provider. Connecting your own OpenAI or Claude key needs a paid plan. The app is in open beta, so features and pricing may change.
What usually breaks: the agent never calls a tool because the tool descriptions are vague. Write descriptions that say "use when…" and name the tool in the instructions.
Build it: Make AI agents guide

20. Ask Claude who owes you money (MCP)

Connect Claude or ChatGPT to the Make MCP server and ask in plain language: "Who's more than 14 days overdue?" A Make scenario reads your invoice sheet and returns the answer.

Who it's for: owners who already use Claude or ChatGPT and want answers from their own data.
Trigger → modules: a scenario scheduled On demand with a scenario input (minimum days overdue) → Google Sheets Search Rows → filter → Array aggregator → Scenarios Return output.
Credits: about 2–3 per question, counted from the modules. The AI app's own usage is billed by that app.
Plan fit: the pricing table lists the MCP server and scenario inputs and outputs on every plan, including Free. Letting the AI build or edit scenarios needs management scopes, which are paid-only.
What usually breaks: the scenario doesn't show up as a tool. It must be active and scheduled On demand, and the connection needs the run scope.
Build it: Make MCP server guide

How to pick your first automation

The best first scenario is small, frequent and low-risk. Five questions help:

Do you do it every week? Copying leads, chasing invoices and filing receipts come up again and again. A once-a-year task isn't worth a scenario.
Is the data already in one place? Examples that start from a Google Sheet (6, 7, 9, 10, 16) are the easiest, because you can see and fix the data yourself.
Who sees the result? Start with something that reaches only you or your team: a digest (7), a Slack alert (1) or drafts you send yourself (9). Move to customer-facing emails once you trust it.
Does it fit the Free plan? Free allows 2 active scenarios, 1,000 credits a month and runs at most every 15 minutes (make.com/en/pricing, checked 3 October 2026). An instant trigger or a daily schedule keeps credit use low.
Can you test it with fake data? Use a copy of the sheet and a test channel or your own email address.

If you're unsure, start with the free Overdue Invoice Digest (7) or Form responses to Slack (1). Both take a few modules, reach only you or your team, and teach the pattern most of the other examples use: search a sheet, then do something with each row. New to Make altogether? Read Make.com for beginners first.

If you don't have a Make account yet, create a free Make account (affiliate link). Everything marked "Free" above runs on it.

Affiliate disclosure: links marked "affiliate link" include our partner code. If you sign up or later buy a paid plan through them, Flowpaja may earn a commission at no extra cost to you. More on the tools we use: best tools for Make automation.

Importing a template instead of building from scratch

Most of the "Build it" links above are step-by-step guides, and the templates come as a Make blueprint (a JSON file) you import into your own account:

Create a new scenario in Make and choose Import blueprint. It's in the upper-right corner of the Scenario Builder; older tutorials show it in the bottom toolbar.
Pick the .json file. It has to be under 2 MB, and a word processor that turns straight quotes into curly ones makes it invalid.
Reconnect every module. Blueprints carry modules and mappings, never connections, so each module that needs one shows a warning until you pick your own Google, Slack or Gmail connection.
Reselect your own sheet, channel or folder, set the schedule, and test with Run once on fictional data before switching it on.

The full walkthrough, including what to do with JSON text instead of a file: how to import a Make blueprint.

What these cost to run

On Make's Free plan, all 20 examples cost nothing to build and test. What limits you is the 1,000 credits a month, the 2 active scenarios and the 15-minute minimum interval. A few rough monthly figures, using the counts above:

Setup	How we count it	Rough credits a month
Overdue digest (7), daily	1–2 on quiet days, about 4 with overdue invoices	30–120
Invoice reminders (6), daily, 20 reminders	30 runs × 1 + 20 × 2	About 70
Tally → Sheets (4), 100 responses	100 × 3, nothing on empty checks	About 300
Form → Slack (1), hourly checks, 50 responses	720 checks + 50	About 770

The last row shows the usual trap: scheduled checks, not the actual work, use most of the credits. Checking every two hours halves that, and an instant trigger removes it. Before you switch a scenario on, put your own numbers into the Make credits calculator. Make credits explained has 12 ways to use fewer.

Plan check: none of the 20 examples needs a paid-only feature. According to Make's pricing table (3 October 2026), the MCP server, AI Agents (beta), the AI Content Extractor, scenario inputs and outputs, and subscenarios are on every plan, including Free (the Content Extractor's own app docs still say paid plans, so check your account). The Make Code app isn't on Free. Custom variables start on Pro, and custom functions are Enterprise-only. When you outgrow Free, mostly because of a third active scenario or more credits, compare Make with the alternatives in Make vs Zapier vs n8n.

Sources checked (3 October 2026)

make.com/en/pricing: Free plan limits, credit rules (routers and error handlers use no credits) and the per-plan feature table, as seen from a US connection
Make app pages on make.com/en/integrations for Google Sheets, Gmail, Slack, Shopify, Facebook Lead Ads, WhatsApp Business Cloud, Google Calendar, Google Drive, QuickBooks, Xero, OpenAI, Typeform, Tally, Pipedrive, Discord, Stripe and Make AI Agent; apps.make.com docs for HubSpot CRM, Shopify and Google Calendar
The linked Flowpaja guides and templates, for the scenario steps, credit counts and common errors in each example

Don't have a Make account yet? You can build and test this scenario on Make's free plan.

Create a free Make account (opens Make in a new tab)

Affiliate link: Flowpaja may earn a commission at no extra cost to you.

FAQ

What can you automate with Make.com in a small business?

Mostly repetitive work between the apps you already use: sending form leads to a CRM and Slack, invoice reminders and overdue digests, quote follow-up drafts, logging Shopify orders to a sheet, saving Gmail attachments to Google Drive, calendar events from booking forms, daily summary emails, and AI steps such as labelling incoming email. This guide lists 20 examples with their modules and links to step-by-step guides.

What are the best Make.com use cases to start with?

Start with something you do every week that only reaches you or your team, such as a daily overdue-invoice digest, new form responses posted to Slack, or quote follow-up drafts that you send yourself. Once you trust the scenario, move on to customer-facing emails and CRM updates.

Are there free Make.com templates for these examples?

Yes. Flowpaja has sixteen free Make templates: Overdue Invoice Digest, Invoice email from a Sheets row, Form responses to Slack, One quote follow-up draft, Webhook to Sheets with a duplicate check, Quote Reply Signal, Lead capture to Sheets + Slack, Typeform hot-lead alert, Unanswered leads digest, Gmail lead label log, Fillout Docs + PDF, Webflow form dedupe, Tally hot-lead alert, Google Forms to HubSpot create or update, Safe Slack Block Kit alerts, and Sheets write reconciliation. Three fuller templates cost $19 each: Polite Invoice Reminder, Quote Follow-Up Assistant and Lead Router. All are listed on flowpaja.com/templates/.

Can I run these automations on Make's Free plan?

Most of them, at low volume. As of 3 October 2026, Make's Free plan includes 1,000 credits a month and 2 active scenarios, runs scheduled scenarios at most every 15 minutes, and limits files to 5 MB. None of the 20 examples needs a paid-only feature, but connecting your own OpenAI or Claude key to a Make AI agent requires a paid plan.

How many credits does a typical Make automation use?

Roughly 1 credit per module action for each item processed, so a simple three-module scenario uses about 3 credits per new item. Scheduled triggers also use 1 credit per check, even when nothing is new, while routers, filters and error handlers use none. The examples here range from about 2 to 8 credits per item. Check the real numbers in your scenario's History after a test run.

Do I need coding skills to use Make?

No. All 20 examples are built from visual modules, filters and a few built-in functions such as trim() or parseDate(). Make's Code app for JavaScript or Python exists but isn't on the Free plan, and none of these examples needs it.

How do I import a Make blueprint?

Create a new scenario, choose Import blueprint in the upper-right corner of the Scenario Builder and pick the .json file, which must be under 2 MB. Blueprints never include connections, so reconnect each module to your own accounts, reselect your sheets and channels, then test with Run once on fictional data before switching the scenario on.

What is the easiest first automation in Make?

A scenario that searches a Google Sheet once a day and emails only you, such as the free Overdue Invoice Digest, or one that posts new Google Form responses to Slack. Both use 2 to 4 modules, cost only a few credits a run and can't send anything to a customer by mistake.

Send a Gmail email when a new row is added in Google Sheets (Make.com)

Flowpaja — Fri, 16 Oct 2026 11:12:28 +0000

A form response, a lead from a landing page or a manual entry lands in a Google Sheet, and you want an email sent to that person without copy-pasting. The part that goes wrong is not the sending: it is sending the same email twice, or not at all, when rows get sorted, edited or deleted.

This guide contains affiliate links, marked “affiliate link”.

Short answer

Use explicit ready and sent states when eligibility can change after row creation. Choose Search Rows for a status-based work queue. Keep uncertain outcomes for inspection before releasing a row again. Before enabling the scenario, inspect the destination using a fictional input and compare the result with the intended business outcome.

Key facts

Select only rows deliberately marked ready.
Watch New Rows is not a general edited-row trigger.
A failed log after sending does not prove the email was unsent.

Need ready-made spreadsheets as well? The Flowpaja Sheets Bundle has 10 Google Sheets templates (bookkeeping, invoices, CRM, budgets and more) for $39.

What you need

A Make.com account with Google Sheets and Gmail connections. No account yet? Create a free Make account (affiliate link).
A Google Sheet with a header row in row 1
These columns: Name, Email, Topic, Status, Sent at
An email text you are happy to send automatically

Ad disclosure: links marked "affiliate link" are ads. If you sign up or buy through them, Flowpaja may earn a commission at no extra cost to you.

Watch New Rows or Search Rows?

Make gives you two ways to pick up new rows, and the choice matters more than any other setting in this scenario.

Google Sheets – Watch New Rows remembers where it stopped, by row position, and returns whatever is below that point. It is simple and it keeps credit use low. It also trusts the position blindly: sort the sheet, delete a row above the marker, or insert a row in the middle, and it can skip rows or pick up old ones again. It also ignores edits to rows it has already seen, and Make's documentation notes that a blank row stops it from processing the rows below it. Older tutorials sometimes call it Watch Rows.

Google Sheets – Search Rows on a schedule looks at the sheet each time and asks a plain question: which rows have no status yet? It does not remember anything, so there is nothing to get out of sync. It uses a few more credits on quiet days, but it recovers by itself after a failed run.

For anything where a duplicate email would be embarrassing, use Search Rows with a Status column. The build below does that.

Start with the existing setup reference Start with this live narrow pattern and read its own setup, test scope and limits before adapting it.

Open the free reference

Step-by-step build

1. Prepare the sheet

Leave the Status column empty for new rows. Make sure the header names have no trailing spaces, because Make shows them as field names and a stray space is annoying to debug later.

2. Add Google Sheets – Search Rows as the first module

Select the spreadsheet and the sheet tab. Set "Table contains headers" to yes. Set a limit, for example 20, so a big backlog does not send hundreds of emails in one run. Put the scenario on a schedule, for example every 15 minutes, using the clock icon on the module.

3. Filter for rows that still need an email

Click the link after the module and add a filter with two conditions, combined with AND:

Status, equal to nothing (an empty value). Depending on how your sheet returns empty cells, "Does not exist" may work better than "Equal to". Test both on a real empty row.
Email, matches pattern: ^[^@\s]+@[^@\s]+\.[^@\s]+$

The second condition keeps half-typed rows from reaching Gmail.

4. Mark the row as "sending"

Add Google Sheets – Update a Row. Set Row number to the row number from the Search Rows output, and write sending into the Status column. This step comes before the email, on purpose: if the scenario crashes during sending, the row is no longer empty and will not be picked up again.

5. Send the email with Gmail – Send an email

To: {{trim(2.Email)}}. Fill in Subject and Body contents, and map fields into the text, for example "Hi {{2.Name}}, thanks for your message about {{2.Topic}}." Body contents accepts HTML tags if you want links or formatting. The 2. prefix is the module number from this example, so use the mapping panel for yours.

6. Update the row again

Add a second Google Sheets – Update a Row. Same row number, Status set to sent, and Sent at set to {{formatDate(now; "YYYY-MM-DD HH:mm")}}.

7. Handle failures

Right-click the Gmail module and add an error handler. Route it to Google Sheets – Update a Row, with the row number from step 2 and Status set to failed, then end the route with the Skip error handler (called Ignore in older versions) so the run continues with the next row. A failed row is now visible in the sheet and does not block the others.

8. Test

Add a row with your own email address, click Run once, and confirm that the Status moves to sent. Run it a second time right away: nothing should happen. That second run is the real test.

Common errors and fixes

The same person gets the email twice. Usually the status update failed after the email went out, or two copies of the scenario run on the same sheet. Update the status before sending, as in step 4, and check that you have not cloned the scenario and left both active.

Search Rows returns nothing, but the sheet has new rows. The filter on Status does not match how Make reads empty cells, or the module points at the wrong sheet tab. Open the output of a Run once and look at what the Status field actually contains. A single space counts as content.

The wrong row gets updated. The row number was taken from a different module than the one that found the row, or someone sorted the sheet while the scenario ran. Always use the row number from the Search Rows bundle in the same run, and avoid sorting the live sheet. A separate view or tab for sorting keeps the working sheet stable.

"Invalid to header" from Gmail. The Email cell contains a trailing space, a line break or two addresses. Wrapping the field in trim() fixes most cases, and the pattern filter in step 3 catches the rest.

429 or quota errors from Google Sheets. Too many reads and writes in a short time. Lower the limit in Search Rows, and consider adding Tools – Sleep for a second or two between rows. Make usually treats a 429 as a rate-limit error and retries later, so it does not count like an ordinary error.

"You have reached a limit for sending mail" from Gmail. Google caps how much one account can send. Google's help pages give roughly 500 emails or recipients per day for a personal Gmail account and up to 2,000 messages per day per user on Google Workspace, with lower limits for trial accounts. Treat these as approximate, check Google's current documentation, and keep the Search Rows limit well below your daily cap.

Don't have a Make account yet? You can build and test this scenario on Make's free plan.

Create a free Make account (opens Make in a new tab)

Affiliate link: Flowpaja may earn a commission at no extra cost to you.

FAQ

Can I use Watch New Rows instead?

Yes, if the sheet only ever grows at the bottom and nobody sorts or deletes rows. Add the Status update anyway, as a record of what was sent.

Can it run the moment a row is added?

Watch New Rows and Search Rows run on a schedule. The instant Watch Changes module only reacts to edits a person makes in Google Sheets and does not watch for new rows, so it does not fit here. For instant triggers, a small Google Apps Script that calls a Make webhook on edit works. That is a different build.

How do I send an email again?

Clear the Status cell for that row. The next run picks it up.

Can I send from an alias or a shared mailbox?

The Send an email module has a From field for a custom sender address. It has to be an address the connected Gmail account is allowed to send from, such as an alias set up in that Gmail account.

Make WhatsApp error 133010 "Account not registered": register the sender

Flowpaja — Fri, 16 Oct 2026 10:59:04 +0000

Fix [400] [133010] Account not registered in Make WhatsApp Business Cloud: run Register a Sender once with a 6-digit PIN, plus 133016, 133005 and 133006.

Updated 15 Oct 2026 · ~6 min read

Disclosure: this guide has one affiliate link to Make, marked "affiliate link", and mentions our Fiverr fix service. Error messages, settings and limits come from Make Help Center / app docs, Meta WhatsApp Cloud API docs and Make Community thread 105136 checked on 15 October 2026; anything we could not confirm is flagged for review before publishing. We did not reproduce these in a live Make scenario for this guide. Prices, where mentioned, are as seen from the US.

Short answer: [400] [133010] (#133010) Account not registered means the phone number is known to Meta but has not been registered for the WhatsApp Cloud API, so it can't send yet. In Make, add WhatsApp Business Cloud › Register a Sender, pick the same connection and phone number, enter a 6-digit PIN, run it once, then delete the module and retry.

Everything here works on Make's Free plan. The steps come from Make's WhatsApp Business Cloud troubleshooting page and Meta's Cloud API docs; we did not register a number ourselves for this guide.

What 133010 means

Meta's Cloud API error code list gives 133010 as "Phone number not registered on the WhatsApp Business Platform." and the fix as "Register the phone number before trying again." Make's troubleshooting page shows the error as [400] [133010] (#133010) Account not registered and explains that the number "has been added to your Facebook Business Portfolio but hasn't been officially registered as a sender on the WhatsApp Business Platform."

Meta's registration docs say you can only register a number through the API, not in WhatsApp Manager or the App Dashboard. That is why Make has a module for it. The error usually shows up on Send a Template Message or Send a Message, often right after a new connection or a new number.

Fix: register the sender in Make

In the scenario, add WhatsApp Business Cloud › Register a Sender (you can put it on a new, unconnected spot in the canvas).
Select the same Connection and the Sender ID (phone number ID) that the failing module uses.
Enter a 6-digit PIN. If two-step verification is already on for the number, it must be that PIN. If it isn't, the 6 digits you enter become the new two-step verification PIN, so write it down.
Right-click the module and choose Run this module only, once.
When it succeeds, delete the Register a Sender module and run the original scenario again.

Don't leave Register a Sender inside the running scenario. Meta limits registration to 10 requests per business number in a 72-hour moving window; after that it returns error 133016 and blocks registration of that number for the next 72 hours.

If Register a Sender fails or 133010 comes back

You see	What Meta's docs say	What to do
`133016`	Over 10 registration requests in 72 hours	Wait 72 hours; stop any scenario that registers on every run
`133005`	Two-step verification PIN incorrect	Use the correct PIN. To reset it, Meta says to disable two-step verification, then set a new PIN
`133008` / `133009`	Too many PIN guesses / PIN entered too quickly	Wait the time given in the error details
`133006`	Phone number needs to be verified before registering	Verify the number first (Make has Verify a Sender: request a code by SMS or voice, then verify it)
`133015`	The number was recently deleted and deletion has not finished	Wait 5 minutes, then try again

Also check the number's status in WhatsApp Manager. A Make Community answer in thread 105136 suggests confirming the number shows as Active there.

Make's two-step verification note

Make's WhatsApp Business Cloud requirements say you must turn off two-step verification for the WhatsApp Business number if it's enabled, and its troubleshooting page has a separate error for certificate creation when two-factor authentication is still on. Meta's registration endpoint, on the other hand, takes the existing PIN if two-step verification is on. If registration fails with a PIN error, follow Make's note: turn two-step verification off in WhatsApp Manager, then register again with a new 6-digit PIN.

After it works

New chats must start with Send a Template Message; Make's docs say you can use Send a Message only after the customer has replied to a template.
Until Meta has reviewed your business and display name, Make's docs mention a limit of 5 business-initiated test messages every 24 hours.
Coexistence numbers (the WhatsApp Business app and Cloud API on one number) have their own connection mode in Make; see Make WhatsApp automation.

Sources checked (15 October 2026)

Make apps: WhatsApp Business Cloud troubleshooting (Account not registered), WhatsApp Business Cloud (requirements, Register/Verify a Sender)
Meta for Developers: Cloud API error codes, Register a business phone number (updated 26 Jun 2026)
Make Community: 105136, 93457

Don't have a Make account yet? You can build and test this scenario on Make's free plan.

Create a free Make account (opens Make in a new tab)

Affiliate link: Flowpaja may earn a commission at no extra cost to you.

FAQ

What does WhatsApp error 133010 mean?

Meta's error list says the phone number is not registered on the WhatsApp Business Platform. The number is in your business portfolio but not registered as a Cloud API sender.

How do I fix 133010 in Make?

Add WhatsApp Business Cloud Register a Sender, select the same connection and phone number, enter a 6-digit PIN, run it once, then delete the module and retry.

How many times can I register a number?

Meta allows 10 registration requests per business number in a 72-hour moving window. After that you get error 133016 and must wait 72 hours.

Which PIN do I use?

If two-step verification is on, the existing PIN. If it is off, the 6 digits you enter become the new PIN. Make's requirements say to turn two-step verification off for Make connections.

Make Instagram IM006 "Token already exist / Token not found": what to check

Flowpaja — Fri, 16 Oct 2026 10:55:15 +0000

IM006 Token already exist / Token not found when connecting Instagram for Business in Make: what reports show, what you can check, and what to send support.

Updated 15 Oct 2026 · ~6 min read

Disclosure: this guide has one affiliate link to Make, marked "affiliate link", and mentions our Fiverr fix service. Error messages, settings and limits come from Make Help Center / app docs and Make Community threads 115997, 90137 and 100489 checked on 15 October 2026; anything we could not confirm is flagged for review before publishing. We did not reproduce these in a live Make scenario for this guide. Prices, where mentioned, are as seen from the US.

Short answer: IM006 with "Token already exist." / "Token not found." appears when Make finishes an OAuth sign-in (Instagram for Business, Facebook, QuickBooks) but cannot save the token. Make's Help Center does not document this code. In every Make Community thread we found, deleting and recreating the connection did not fix it, and the answer was a ticket to Make support or a fix on Make's side. Check the few things you can check yourself, then open a ticket with the evidence below.

We could not reproduce IM006 for this guide. Everything here comes from Make's Instagram app docs and Make Community threads.

What the error looks like

The callback page shows a JSON body like this (seen in Make Community, January 2026):

{"detail":"Token not found.","message":"Token already exist.","code":"IM006"}

Some reports say "Token already exists." with an s. In thread 115997 (September 2026) the Facebook/Instagram authorization completed, the callback to Make failed with IM006, and Make could not load the Facebook Page or Instagram Business assets.

What Make Community reports show

Thread	App	What happened
90137 (Aug 2025)	Facebook	Removed Make from Facebook Business Integrations, deleted old connections, tried incognito and other browsers. No fix posted.
100489 (Jan 2026)	QuickBooks Online	A Make community manager said the development team was aware connections to QuickBooks were not being created and was investigating with high priority.
115997 (Sep 2026)	Instagram for Business (Facebook login)	Permissions confirmed, connection deleted and recreated, reauthorized. A community helper called it an internal connection issue on the Make account side and pointed to a Make Customer Care ticket.

So far, the pattern is: the same error across different OAuth apps, reconnecting does not help, and the fix comes from Make. That is why this guide does not promise a reconnect trick.

Check these first (10 minutes)

These come from Make's Instagram for Business (Facebook login) app docs. They don't fix IM006 itself, but they rule out the setup problems that look similar, and support will ask about them.

Business account, not Creator. Make's docs say creator accounts are not supported. Switch the Instagram profile to a business account.
Page link. The Instagram business account must be connected to a Facebook Page, and you must sign in with a Facebook account that has admin-level access to that Page.
Custom app only: if you turned on Show advanced settings and entered your own client credentials, the redirect URI in your Meta app must be https://www.integromat.com/oauth/cb/facebook. See Make OAuth redirect URLs.
One clean attempt in a private window. A community helper suggested a private browser window so cookies and cache don't affect the OAuth flow. Do it once; repeating it many times did not help anyone in the threads.
Other connections still work? If your existing Facebook or Instagram connections in the same Make organization still run, don't delete them while you troubleshoot. Rename the new one instead.

Open a Make support ticket with this evidence

Make support has access to internal systems and logs; community members do not. Open a ticket at make.com/en/ticket and include:

The full JSON from the callback page (screenshot and text), with the time and your time zone.
Your Make zone (for example eu1 or us1), organization and team.
The app and connection type (Instagram for Business (Facebook login), default or custom client).
What you already checked from the list above.
Whether older connections to the same Facebook account exist and still work.

While you wait, keep the scenario's other parts running: if posts or comments must not be lost, log them in a Google Sheet or send them to Slack until the Instagram module works again.

Not IM006? Similar Instagram connection problems

The Page dropdown is empty after connecting: Make's docs say this is often because the Facebook Page is not properly connected to the Instagram business account in Meta Business Suite.
Publishing fails: accounts linked to a Page that requires Page Publishing Authorization can't publish until it is completed, and media must be on a publicly accessible URL (not Google Drive).
Insights are empty: Make's docs note insights are unavailable for Instagram users with fewer than 100 followers.

For setup and ideas see Make Instagram and Facebook automation.

Sources checked (15 October 2026)

Make apps: Instagram for Business (Facebook login)
Make Community: 115997, 90137, 100489, 100683
Make Help Center search for IM006: no article (15 Oct 2026)

Don't have a Make account yet? You can build and test this scenario on Make's free plan.

Create a free Make account (opens Make in a new tab)

Affiliate link: Flowpaja may earn a commission at no extra cost to you.

FAQ

What is IM006 in Make?

An error on the OAuth callback with Token already exist and Token not found. Make's Help Center does not document it. Community reports cover Instagram for Business, Facebook and QuickBooks.

Does deleting and recreating the connection fix IM006?

Not in the Make Community threads we found. Users had tried it, plus other browsers and incognito, without success.

Who can fix IM006?

Make support. In the QuickBooks case Make's team said they were investigating; in the Instagram case a helper pointed to a Customer Care ticket because support can see internal logs.

Are Instagram Creator accounts supported in Make?

No. Make's Instagram for Business docs say creator accounts are not supported; switch to a business account linked to a Facebook Page.

Make Airtable 422 INVALID_VALUE_FOR_COLUMN: match the value to the field type

Flowpaja — Fri, 16 Oct 2026 10:50:43 +0000

Fix Airtable 422 INVALID_VALUE_FOR_COLUMN in Make: what each 422 type means, the value each field type takes, Smart links (typecast) and HTTP 422s.

Updated 15 Oct 2026 · ~8 min read

Disclosure: this guide has one affiliate link to Make, marked "affiliate link", and mentions our Fiverr fix service. Error messages, settings and limits come from Make Help Center / app docs, Airtable API docs and Make Community threads 59826, 79365 and 115822 checked on 15 October 2026; anything we could not confirm is flagged for review before publishing. We did not reproduce these in a live Make scenario for this guide. Prices, where mentioned, are as seen from the US.

Short answer: An Airtable 422 in Make means Airtable understood the address but rejected the data. With INVALID_VALUE_FOR_COLUMN the value you mapped does not fit the field type: text into a number field, the text true into a checkbox, a date-time into a date-only field, a name instead of a record ID in a linked field. Open the module's input bundle in History, find the field Airtable names, and convert the value to the format that field type takes.

Everything here works on Make's Free plan. We did not reproduce these errors in our own Make account; they come from Airtable's API docs and threads in Make Community.

What a 422 from Airtable means

Airtable's API errors page lists 422 Invalid Request: "The request data is invalid. This includes most of the base-specific validations." Airtable sends a type and a message with it, and that type tells you which problem you have. Make shows it in the module's error, usually as [422] followed by Airtable's message.

The type INVALID_VALUE_FOR_COLUMN with a message saying a field cannot accept the provided value is the most common one in Make scenarios. Airtable's public docs do not list this type in the errors table, so the exact wording can vary.

422 types and what each one means

Type	What it means	Fix in Make
`INVALID_VALUE_FOR_COLUMN`	The value does not fit the field type	Convert the value (table below)
`INVALID_MULTIPLE_CHOICE_OPTIONS`	A select option that does not exist yet	Match the option exactly, or let Airtable create it (typecast, see below)
`UNKNOWN_FIELD_NAME`	The field was renamed, or deleted and recreated with a new field ID	Refresh the module and remap; see new fields not showing
`INVALID_REQUEST_UNKNOWN`	Airtable could not validate the request body and does not say which parameter	Mostly HTTP / Make an API Call: check the raw JSON (below)
`FAILED_STATE_CHECK`	IDs in the path don't belong together (for example a view from another table)	Re-select base, table and view

Field types and the value Airtable expects

From Airtable's field model reference. Check the field type in Airtable first, then compare it with what Make actually sent in the input bundle.

Airtable field	Send	Typical Make mistake
Number, Currency, Percent	A number	Text such as `1 200,50` or `$40`. Use `parseNumber()`; see invalid number from form answers
Checkbox	`true` / `false` (boolean)	Text such as `Yes` or `true` from a form
Date	An ISO 8601 date string	A local format like 03/09/2026; Airtable Community also reports rejections when a date with a time goes to a field without Include time
Single select	The option name as text	A spelling or case difference from the existing option
Multiple select	An array of option names	One comma-separated text
Link to another record	An array of record IDs (`rec…`)	Names instead of IDs without Smart links on

Fix it step by step

Open the failed run in History, click the Airtable module's bubble and read the input bundle. That is what Airtable received, not what the mapping panel shows.
Find the field named in the error message. If the message has a field ID (fld…), look it up in Airtable's field settings or the API docs for the base.
Check its type in Airtable, then convert in the mapping: parseNumber() for numbers, formatDate() for dates, a boolean for checkboxes, split() for multiple selects.
Empty values: if a source field may be empty, map it with ifempty() or leave it out. To clear a field in Update a Record, Make's docs say to use the erase function.
Run the module again with Run this module only using the same input.

A rich text field that rejected a long text in Community thread 59826 got the same answer from helpers there: check the field type in Airtable, because the problem is in what the field accepts, not in Make.

Smart links and typecast

Airtable's API has a typecast parameter: Airtable then does best-effort conversion from text and can create a select option that does not exist yet. It is off by default. Airtable's support article says that in Make this option is called Smart links. Make's own Airtable docs describe Smart links on Create a Record and Update a Record as entering names instead of record IDs in linked-record fields, with the linked record created when there's no match.

Typecast is not a fix for every 422. Airtable notes that creating select options with typecast needs creator permissions on the base, and a value that can't be parsed still fails. Fix the value first; use Smart links when you really want new options or names in linked fields.

422 with HTTP or Make an API Call

When you build the JSON yourself, the type is often INVALID_REQUEST_UNKNOWN with "Invalid request: parameter validation failed. Check your request data." In thread 115822 (September 2026) the same webhook request worked with curl but failed from the HTTP module. The replies suggested checking:

Typographic quotes (“ ”) in a body pasted from a document or chat. The body is then not valid JSON.
Content type: with Body type Raw, choose JSON in the module, and don't add a second Content-Type header by hand.
Mapped values: read the runtime input bundle, not the module settings.
Build the body with JSON › Create JSON instead of a hand-written string.

That thread has no confirmed root cause yet. For general JSON problems see Make Parse JSON errors.

Sources checked (15 October 2026)

Airtable Web API: Errors, Field model, Create records (typecast)
Airtable Support: Airtable API: Common troubleshooting
Make apps: Airtable (Smart links, Use Column ID, erase)
Make Community: 59826, 79365, 115822

Don't have a Make account yet? You can build and test this scenario on Make's free plan.

Create a free Make account (opens Make in a new tab)

Affiliate link: Flowpaja may earn a commission at no extra cost to you.

FAQ

What does INVALID_VALUE_FOR_COLUMN mean?

The value Make sent does not fit the Airtable field type, for example text in a number field or the text true in a checkbox. Convert the value to the format the field takes.

Does Smart links fix Airtable 422 errors?

Sometimes. Airtable's support says Smart links is Make's equivalent of typecast, which converts text and can create new select options. Make's docs only describe it for linked records, and unparseable values still fail.

How do I see what Make sent to Airtable?

Open the failed run in History and click the Airtable module's bubble. The input bundle shows the values Airtable received.

Why does the HTTP module get 422 when curl works?

Usually the body differs: curly quotes, a wrong or double Content-Type, or a mapped value that is empty at run time. Build the body with Create JSON and compare the requests.

Make Airtable 429 "Rate limit exceeded": per-second limit or monthly API calls?

Flowpaja — Fri, 16 Oct 2026 10:44:37 +0000

Fix Airtable 429 in Make: 5 requests per second per base vs the monthly API call limit, "Failed to load data (429)", and how to slow scenarios down.

Updated 15 Oct 2026 · ~7 min read

Disclosure: this guide has one affiliate link to Make, marked "affiliate link", and mentions our Fiverr fix service. Error messages, settings and limits come from Make Help Center / app docs, Airtable API docs and Make Community threads 101017 and 108653 checked on 15 October 2026; anything we could not confirm is flagged for review before publishing. We did not reproduce these in a live Make scenario for this guide. Prices, where mentioned, are as seen from the US.

Short answer: An Airtable 429 in Make means Airtable refused the call, not Make. There are two different 429s: the per-second limit (5 requests per second per base; Airtable then wants a 30-second wait) and the monthly API call limit of your Airtable plan (it lasts until the next month). Find out which one you hit first, because only the first one goes away with Sleep modules and retries.

Everything below works on Make's Free plan. We did not reproduce a 429 in our own Make account for this guide; the error texts come from Airtable's API docs and Make Community threads.

What Airtable's 429 means

Airtable's API docs say: "The API is limited to 5 requests per second per base." There is also a limit of 50 requests per second for all traffic using personal access tokens from one user or service account. When you go over, Airtable answers 429 Too Many Requests with the type RATE_LIMIT_REACHED and the message "Rate limit exceeded. Please try again later", and you "will need to wait 30 seconds before subsequent requests will succeed."

Make shows a 429 as a RateLimitError. Make's rate limit help page says the rate limit error in Make corresponds to HTTP 429, and it names Airtable as one of the apps that often hits it when a scenario processes many records in a short time.

Airtable's own troubleshooting article adds a second 429: when you have used up the plan's monthly API call limit, the error type is PUBLIC_API_BILLING_LIMIT_EXCEEDED and the fix is to wait for the first day of the next month or change plan. Airtable's troubleshooting article gives the monthly limits: 1,000 API calls on the Free plan and 100,000 on the Team plan; Business and Enterprise plans have no monthly call limit.

Which 429 do you have?

What you see	Likely limit	What fixes it
429 in the middle of a run that handles many records; later runs work	5 requests per second per base	Fewer calls per second: bulk modules, smaller batches, Sleep, Retry handler
429 on the first Airtable call, every run, even with one record	Monthly API call limit of the Airtable plan (`PUBLIC_API_BILLING_LIMIT_EXCEEDED`)	Check API usage in the Airtable workspace settings; wait for next month or upgrade
"Failed to load data (429)" when you open the Table dropdown in a module	Either of the above, or a base-specific problem	Test the metadata call with Make an API Call (see below)

In Make Community thread 108653 (May 2026) the user could not pick a table in Watch Records, opened the workspace settings in Airtable and found that the monthly API calls were used up. That is the second row.

"Failed to load data (429)" on one base only

Thread 101017 (January 2026) describes the Table dropdown in Airtable Search Records failing with "Failed to load data (429)" for one base while another base on the same connection worked. A community member suggested testing Airtable's metadata endpoint directly:

Add Airtable › Make an API Call with the same connection.
URL: v0/meta/bases/{baseId}/tables (the base ID starts with app and is in the Airtable URL). Method: GET.
Click Run this module only.

If this returns 200, the problem is in how the module loads the list, so open a ticket with Make support. If it also returns 429, the answer comes from Airtable, so take the evidence to Airtable support. In that thread the direct call also returned a 429 RateLimitError with origin Airtable, and the user took it to Airtable. The thread has no confirmed fix.

What Make does after a 429

If the Airtable module has no error handler, Make's help page lists what happens:

Scheduled scenario: Make pauses the next scenario run for 20 minutes. With incomplete executions enabled, it also reruns the stored incomplete execution with exponential backoff.
Instant scenario (webhook trigger): Make reruns the execution with exponential backoff.

Turn on Store incomplete executions in Scenario settings so the failed bundle is kept. A RateLimitError is one of the error types Make retries automatically from incomplete executions.

How to stop hitting the per-second limit

Use bulk modules. Make's Airtable app has Bulk Create Records (advanced), Bulk Update Records (advanced) and Bulk Upsert Records (advanced). Airtable's create and update endpoints take up to 10 records per request, so batching can cut the number of calls. Make's module docs don't say how the Bulk modules split larger arrays, so test with your own data. Put an aggregator in front to build the array (see iterator vs aggregator).
Process fewer records per run. Make recommends a limit of up to 20 records per run for frequently scheduled scenarios; set it in the trigger's Limit field.
Slow instant scenarios down. Set Maximum runs to start per minute on the instant trigger (the lightning icon or Schedule setting).
Add a Sleep module before the Airtable module that fails. Make's Sleep waits up to 300 seconds. At 5 requests per second per base, even a 1-second pause per bundle keeps a single route well under the limit.
Add a Retry error handler (formerly Break) on the Airtable module with automatic completion, so a rare 429 is retried later instead of failing the run. Don't use Skip (formerly Ignore) here: it drops the record.
Count every scenario. The 5 per second limit is per base, so two scenarios writing to the same base at the same moment share it. Spread their schedules.

Read requests can also be cut: one Search Records with a formula instead of a Get a Record per bundle. Airtable's docs suggest a caching proxy if you expect a high read volume.

If you hit the monthly limit

No amount of Sleep fixes this one. Open the Airtable workspace settings and check API usage (the Make announcement points there). Then either wait until the limit resets on the first day of next month, upgrade the Airtable plan, or cut the calls: polling triggers such as Watch Records call Airtable on every scheduled run even when nothing changed, so a 1-minute schedule spends calls all day. A longer interval, or a webhook pushed from an Airtable automation, uses far fewer.

The same thinking applies to Make credits. See Make credits explained.

Sources checked (15 October 2026)

Airtable Web API: Rate limits and Errors
Airtable Support: Airtable API: Common troubleshooting (TOO_MANY_REQUESTS, PUBLIC_API_BILLING_LIMIT_EXCEEDED)
Make Help: Fix rate limit errors; Make apps: Airtable
Make Community: 101017, 108653, 66395

Don't have a Make account yet? You can build and test this scenario on Make's free plan.

Create a free Make account (opens Make in a new tab)

Affiliate link: Flowpaja may earn a commission at no extra cost to you.

FAQ

What does a 429 from Airtable mean in Make?

Airtable refused the request because a limit was hit. Make shows it as a RateLimitError. It is either the 5 requests per second per base limit or the monthly API call limit of the Airtable plan.

How long do I have to wait after an Airtable 429?

For the per-second limit, Airtable's docs say to wait 30 seconds before new requests succeed. For the monthly limit (PUBLIC_API_BILLING_LIMIT_EXCEEDED) the limit resets on the first day of the next month.

Does Make retry an Airtable 429 automatically?

With incomplete executions enabled, yes: RateLimitError is retried with exponential backoff. Scheduled scenarios also pause the next run for 20 minutes.

Why does the Table dropdown say Failed to load data (429)?

Make could not load the table list from Airtable. Test GET v0/meta/bases/{baseId}/tables with Airtable Make an API Call: a 429 there points to Airtable, a 200 points to Make support.

A HubSpot 409 Is a Record-Matching Problem

Flowpaja — Fri, 16 Oct 2026 07:40:34 +0000

Some links are affiliate links. If you sign up, Flowpaja may earn a commission at no extra cost to you.

A contact creation fails with a 409, so the tempting repair is to add another retry. That changes the timing of the request without changing its meaning: create a contact for an email address that already belongs to a contact. The useful question is which record the workflow should have updated.

Consider a fictional enquiry from Morgan Example. The form sends a name, an email and a project note. Morgan already exists in HubSpot because someone entered the contact last month. The automation should preserve that relationship while recording the new enquiry. Repeating the create request cannot express that intention.

Treat the conflict as evidence about identity. First establish which email was submitted, where it was mapped and which existing record HubSpot identifies. Then choose the smallest repair that preserves the right contact and its existing sales context.

Start with the failed write

Open the failed execution and inspect the input of HubSpot CRM's Create a Contact module. Copy the actual email value into your investigation notes. An email-looking question label in the form does not prove that the standard HubSpot Email property received a value.

Read the full error. If it provides an existing contact ID, open that record in HubSpot. Compare its primary email, additional email addresses and name with the submission. Do not merge contacts simply because the error contains a record ID. A merge changes the CRM's identity history and is not a routine retry strategy.

Also separate the error families. A 409 contact conflict and a 400 invalid property value require different repairs. If the latter identifies a dropdown, compare the submitted value with the property's internal option value. A visible label on a form is not necessarily the value the CRM API expects.

Choose the write behavior you need

For a workflow that handles new and existing contacts identically, Create or Update a Contact is the simpler starting point. Map the normalized email into the standard Email property, then map the fields the form is allowed to change. Make's HubSpot CRM reference lists the available contact modules.

Normalize once in concept, and use the same result for every lookup and write. lower(trim(email)) removes surrounding whitespace and case differences. Select your actual email token in Make's mapping panel; email here describes the value, not a universal field path.

Avoid replacing the email with a custom work-email field while leaving the standard property empty. The contact-matching behavior relies on the standard property. Also stop incomplete submissions before the CRM write. A nonempty, plausible email is an intake requirement; an address merely containing an at-sign is only a basic screen, not proof of deliverability.

Search first when the next action depends on newness

An upsert alone does not establish whether a Slack alert should say “new contact.” If new and existing contacts need different downstream actions, add Search for Contacts before the decision. Use an exact Email equality condition with the same normalized value. Leave a broad free-text query out of the identity lookup.

Test the no-match behavior before adding the create branch. A search that emits no bundle cannot reach a router merely because the router has a “missing ID” condition. Test whether your current HubSpot search module continues on zero results, and which supported setting or lookup response provides a bundle for that case. Do not copy Google Sheets' empty-bundle behavior onto HubSpot by assumption.

Once the search result can reach the decision, a found ID belongs on Update a Contact. A no-match path can use Create or Update a Contact to tolerate a contact that appears between lookup and write. Keep any “new person” notification policy separate from the upsert's success status.

Give the form limited authority

A resubmission might contain a better phone number. It should not necessarily replace the contact owner, lifecycle stage or carefully maintained company details. Write down which properties intake owns before mapping everything the form offers.

Make update modules skip empty mapped values by default. An unanswered optional question therefore should not be treated as an instruction to clear a known value. For deliberate clearing, use Make's erase keyword rather than an ordinary blank. Test explicit clearing on the exact HubSpot property and connector version before relying on it. Keep a fictional record for this check.

This distinction matters during repair. Mapping a fallback phrase into an empty field can make the run succeed while polluting a record. A missing phone number does not become a real phone number because the mapping inserts “Not provided.”

Inspect additional emails and overlapping runs

The contact identified by the conflict may have a different primary address. An additional email on that record can explain why a primary-email lookup found nothing but creation still collided. Review the record before deciding whether to update it. The right identity decision is more important than forcing the scenario green.

Two near-simultaneous deliveries create another gap: both lookups may happen before the first contact is visible to search. For an instant-trigger scenario, sequential processing prevents those runs from overlapping within that scenario. It does not serialize another scenario writing to the same CRM, and it does not turn the search into a database lock.

Keep the error visible if identity remains uncertain. Retry can help a temporary connection problem; the same unresolved conflict needs a changed write or an identity decision. Skip drops the failed bundle. If you choose it after an alert, someone still has to recover the missed update.

Test the relationship, not just the badge

Use a disposable contact and a fictional address such as morgan@example.invalid. Submit a new email, submit it again with changed project text, and submit it with surrounding spaces and capitals. Check that the intended contact persists and the changed field is actually present.

Then test an omitted optional field and an existing owner. Both should follow your ownership rules. If the workflow branches on newness, verify that the new-email case reaches the write and that a repeat does not receive the new-contact treatment.

Record the contact ID after each case. That gives a concrete acceptance result: one continuing CRM relationship with controlled updates. Count the credits in actual history; additional searches, alerts and retries change the total.

For Google Forms intake with budget-based Slack routing, the related Lead Router template is an optional starting point. It routes by budget, not by rotation between reps. Follow the full conflict guide before adapting its mappings. If you need a Make account for a disposable test, use Make.

Make Notion invalid_request_url: fix the empty page ID after Gmail and Search Objects

Flowpaja — Thu, 15 Oct 2026 15:55:11 +0000

Fix Notion invalid_request_url in Make: Search Objects shows green but returns no page ID, so the PATCH URL ends at /v1/pages/. Filter, fix the search, use Notion modules.

Updated 14 Oct 2026 · ~12 min read

Disclosure: this guide has one affiliate link to Make, marked "affiliate link", and mentions our Fiverr fix service. Error messages, settings and limits come from Make Help Center / app docs, Notion API docs and Make Community thread 110323 checked on 14 October 2026; anything we could not confirm is flagged for review before publishing. We did not reproduce these in a live Make scenario for this guide. Prices, where mentioned, are as seen from the US.

Short answer: Notion's API returns invalid_request_url when the page URL ends at /v1/pages/ with no page ID. In Make that usually means Gmail → Notion Search Objects looked successful (green ✓1) but the output bundle had an empty ID, and HTTP › Make a request built https://api.notion.com/v1/pages/{{empty}}. Fix the search (and prefer Notion's own Update modules over a bare HTTP PATCH).

Everything here works on Make's Free plan.

What `invalid_request_url` means

Notion's HTTP status reference lists status 400 with code invalid_request_url and message like Invalid request URL when the request URL is not valid. A URL that is literally https://api.notion.com/v1/pages/ (nothing after the last slash) matches that class of failure.

Make Community thread 110323 (June 2026) describes exactly this: Gmail Watch Emails → Notion Search Objects → HTTP PATCH; Search Objects showed green ✓1 while Page ID mapped empty into the HTTP URL.

Green ✓1 is not "one match found"

Community answers in that thread stress: a green check with 1 means the module ran once and returned a bundle, not that a Notion page was found. Open the output bubble. If the ID / page fields are empty, the next HTTP URL will be invalid even though Search Objects did not throw.

Treat "module success" and "business match found" as two different checks. Add a filter after Search Objects: Page ID (or equivalent) Exists before any update module runs.

Fix the Notion search first

Confirm the CRM page or data source is shared with your Make Notion connection (Notion → Add connections for internal integrations; reauthorize public connections after sharing new pages). Make's Notion app docs require sharing databases for them to appear.
Prefer current Data Source modules over Legacy database-item modules. Make documents that from 3 September 2025 Notion API 2025-09-03 uses data_source_id for new modules; Legacy modules still use database_id.
Match the property type in the Search Objects filter. Thread replies note email properties need an email-style filter, not a plain text equals against a mismatched type.
Normalize addresses the same way on both sides (trim, consistent case) before comparing.
Inspect the Search Objects output bundle for the page/data-source item ID you will map.

Prefer Notion Update modules over raw HTTP

Make's Notion app includes Update a Data Source Item, Update a Page, and Make an API Call. Community staff advised using Notion modules (with the existing connection) instead of a generic HTTP module with no Notion auth. That avoids hand-built URLs and missing Notion-Version headers.

If you must use HTTP › Make a request:

Method PATCH, URL https://api.notion.com/v1/pages/<page_id> only when page_id is non-empty (Notion Update page).
Send Notion's required headers (authorization and Notion-Version) as documented by Notion.
Never map a possibly empty ID into the path; filter first.

Safe Gmail → mark Replied pattern

Gmail › Watch emails (or a label watch).
Notion › Search Objects / search data source items by email.
Filter: ID Exists (and optionally status is not already Replied).
Notion › Update a Data Source Item (or Update a Page): set Status / Last contacted.
Optional: log the Message ID in Sheets so repeats do not re-process (see free quote-reply-signal-free for a Gmail-reply → Sheets pattern).

For temporary Notion or HTTP failures after a valid ID exists, attach Retry (formerly Break) and enable incomplete executions, not for empty-ID URL errors, which will not heal by repeating.

Sources checked (14 October 2026)

Notion status codes: invalid_request_url
Notion Update page
Make Notion app (modules, data source migration, sharing)
Community 110323
content_gaps.csv row 12 (priority 5)

Don't have a Make account yet? You can build and test this scenario on Make's free plan.

Create a free Make account (opens Make in a new tab)

Affiliate link: Flowpaja may earn a commission at no extra cost to you.

FAQ

What does invalid_request_url mean in Notion?

Notion's status codes list 400 invalid_request_url when the request URL is not valid, for example /v1/pages/ with no page ID.

Why does Search Objects show green if nothing was found?

A green check with 1 means the module ran and returned a bundle. Open the output: the ID can still be empty.

Should I use HTTP or Notion modules to update a page?

Prefer Notion's Update a Data Source Item or Update a Page with your Make connection. Use HTTP only with a filtered, non-empty page ID and Notion's required headers.