Google Sheets > FloDesk Subscriber & Segment

:bullseye: What is your goal?

I want to create a new subscriber in FloDesk when the email is added to a Google sheet, then also add them to a Segment in FloDesk.

:thinking: What is the problem?

I am not understanding how to do this properly. Everything seems straightforward yet it’s not working.

:test_tube: What have you tried so far?

Welcome to the Make community!

Polling Triggers & Empty “Check Runs”

This is because the triggering module is a POLLING trigger, and not an INSTANT (Webhook) trigger.

If you don’t see any bundles from the trigger module and operations on the rest of the modules, it means there are no new responses (empty output bundle) when the scenario ran to check for new items. This is called a “Check run”.

There are two main types of triggers, Polling (scheduled), and Instant (webhooks). Polling triggers can only run on a schedule. Instant triggers can be run as soon as data is received by the webhook.

  • Polling means Make checks external service for changes (pull changes to Make).
  • Webhook (instant) triggers means external service calls Make when there are new changes (push changes to Make).

The module you are using does not push changes — it’s basically a API request that Make has to occasionally “call” to fetch the latest changes/items.

To find out more on the different types of Trigger modules, see refer to Types of Modules and Webhooks sections of the Make Help Centre.

If you want your scenario to only run when there is new data (and not on a schedule or timed interval), see if your app has an “Instant” or “Webhook” trigger in Make. If not, check if the third-party service has a feature that can send out a webhook when content is created/updated - and then you can point it to a “Custom Webhook” trigger in your scenario.

If you want to re-run your scenario on older data,

Polling Triggers: Epoch Panel & Selecting Older Data

Go to the Epoch Panel, by right-clicking on the trigger module (polling triggers only), and select “Choose where to start” from the list of options in the context menu.

If you select “From now on”, the next time the scenario runs it will only return new data (or nothing if there is no new data).

You can also select other old data to re-run your scenario with next using the “Choose manually” option. This will then show you a list of previous historical items you can select to process the next time the scenario is triggered.

For more information, see

Hope this helps! If you are still having trouble, please provide more details.

— @samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!

Hey @Stefanie_Mullen,

I think the scenario is set up well and looks properly structured. Now just need to test the workflow after checking a few key points.

Key Points:

  1. Confirm the polling interval: Click the clock icon on the trigger module and make sure the polling frequency is properly set.

  2. Verify the correct Google Sheet and tab are selected: Double-check that the sheet, tab, filters, and limits are configured as intended.

  3. Add a filter between the Google Sheet and Flodesk modules: This helps ensure only rows containing a valid email (or other required data) continue through the flow, preventing empty or bad data from causing issues.

  4. Validate field mapping in Flodesk: In the Create or Update Subscriber module, make sure all required fields are mapped correctly.

Next Steps:

  • Save the scenario, then click Run Once (located next to the Save icon).
  • Go to Google Sheet and add a new row by copy/paste to trigger the test.
  • After successful run, review History to check each step of the workflow completed as expected.

If this helps, feel free to mark the answer as a solution :+1:

Thanks so much! This is all really helpful info. Any ideas how to handle this error response:
[429] Rate limit exceed. You can make up to 100 requests per minute.

I’m not sure how to appropriately throttle the requests; we aren’t sending over a huge amount of data from Google sheets to FloDesk…

Hey Stefanie,

add a Break error handler that will retry after a minute (or however long the timeout is).

Handle errors so scenarios don’t stop

You might want to add some error handling to your modules to handle exceptions, so the failing module(s) can automatically be ignored or retried after a short period. By handling any errors by adding a “Error handler” to the module, the scenario won’t throw errors and get switched off.

Error directives can only be added to an error handler route

1. Right click a module and select “Add error handler”

2. Error handlers will appear

For more information on error handling, see:

Hope this helps! If you are still having trouble, please provide more details.

— @samliew