Skip to main content

Make integration: set up and troubleshoot

Send to Make sends data to a Make (Integromat) webhook to trigger scenarios.

Written by Umer Ishaq

Send to Make sends data to a Make (Integromat) webhook to trigger scenarios.

Before you start

  • Account: none. There is nothing to connect.

  • You need: the URL of the Make webhook that should receive the data. It is required. The row needs no particular column.

  • Important: Send to Make writes outside Loopster. With Auto-run on, new values in the first column trigger the row workflow, so data can be sent without you clicking run. Add the column without running it and test one row first. See Run columns safely: Auto-run, test one row, then run the rest.

Do I need to connect Make?

No. Make has no account to connect in Loopster.

How do I send rows to Make?

  1. Click Add column, then Add enrichment.

  2. Open the Export tab. Under Automation, click Send to Make.

  3. Paste the webhook URL into the URL setting.

  4. Check the body. It starts as {}. Change it to the data you want to send. Where a field offers a column list when you press / or @, click a column to use its value. See Map an enrichment's inputs.

  5. Click the arrow next to the main button and choose Add column without running.

  6. Click the play button on one row, then double-click the cell to read the result.

  7. Check the result in Make too.

  8. To run the rest, click the play button on the column header and choose Run all N empty rows in the Run column dialog.

The Add column panel searching for Make. It lists the export Send to Make, marked Free, and the import Webhook and API, which adds rows by receiving rows from any tool, also marked Free.

The Send to Make panel with a required Webhook URL field showing <a href="https://hook.eu1.make.com/" rel="nofollow noopener noreferrer" target="_blank">https://hook.eu1.make.com/</a>..., optional Headers and Body, and Auto-run off. A message at the bottom says to select a column for Webhook URL before running.

How do I check it worked?

  1. Double-click a cell.

  2. The details show the fields of the result. Hover a field and click Add to column to put it in its own column. See Put a result's fields into their own columns.

  3. Also check the result in Make.

Troubleshooting

Quick answer

  1. Auto-run is off, or the column was added without running.

  2. A required input or setting has no value (the panel footer warns).

  3. The cell says Error: open it and read the message.

Nothing happens, or the cells stay empty

What you see: The column exists, but no row has run.

Why it happens: Auto-run is Off (the app says "New rows and values will not run on their own"), or you chose Add column without running.

What to do: Click a row's play button, or use the column header's Run column dialog. See Why didn't my column run?.

The footer says "Select a column for … before running"

What you see: A warning such as "Select a column for … before running." in the panel footer.

Why it happens: A required input or setting (marked with *) has no value. An input can be empty even when a suggestion names a column.

What to do: Click the input, press / and pick a column from the list. Do not close the list with Esc: a / or @ is then left in the field as plain text.

My cells say Skipped

What you see: Skipped in the cells.

Why it happens: Skipped means "Did not run because of filters or missing dependencies."

What to do: Double-click the cell and read the message. Check that every input is mapped to a column, and look under Run Settings for Add run condition ("Only run if this formula resolves to true.").

My cells say Unsatisfied

What you see: Unsatisfied in the cells.

Why it happens: Unsatisfied means "Enrichment ran correctly, but output didn't match expected format."

What to do: Double-click the cell and read the message. Check the input values in that row, and test one row before you re-run many. See What a cell's message means.

A cell says Error

What you see: The cell says Error, and the footer shows a count such as "1 cell failed".

Why it happens: Error means "Crashed, something went wrong." The message is in the cell it happened in.

What to do: Double-click the cell and read the message. Check Make before you re-run, because a re-run runs the action again.

The result did not change after I edited an input

What you see: A finished cell keeps its old result after you change an input.

Why it happens: With Auto-run on, Keep existing results is ticked: "Only errored, empty and new cells run. A completed answer is left alone even when one of its inputs changes."

What to do: Double-click the cell and click Re-run this cell, or click the play button on the column header and choose Overwrite all N rows in the Run column dialog. Read the line under each option first. Either one runs the action on Make again.

Make got the same data twice

What you see: Repeated changes or duplicate entries in Make.

Why it happens: This action writes outside Loopster. Re-run this cell and Overwrite all N rows run it again, so Make may receive the data again.

What to do: Test one row first and check it in Make. Keep Auto-run off until the first row looks right.

What does it cost?

Send to Make is free. The panel shows Free, and the Run column dialog says Spends nothing from your wallet. See Your wallet and keeping spend under control.

Good to know

  • Send to Make is the only Make action in Loopster. It is in the Export tab, under Automation.

  • It is not marked as eligible for a waterfall step.

  • It does not create rows in your table.

  • It writes outside Loopster.

Did this answer your question?