If your automation isn’t running the way you expect it to, we recommend reviewing the troubleshooting guides for the automation platform you’re using first. We’ve linked them below for easy reference:

Zapier Troubleshooting Guide

Make Help Center

Below is an updated list of common issues we’ve seen users run into when building automations in either Zapier or Make:

Zapier

• Find a Message/File Channel: Be sure to use the Membership Entity ID

  field to map the client or company ID. This will ensure the desired channel will be found.

• Mapping data:

  • You will want to use the Custom tab to map data from a previous step. Clicking the

    Custom tab when mapping data will display a list of all previous steps and their output.

  • Be sure not to “hardcode” data such as a client ID, and instead map the data from a previous step.

• Monday.com: Relevant steps will often be Get Item by Column Value and then Change Multiple Columns Value

Make

• Find a Message/File Channel: Be sure to use the Membership Entity ID

  field to map the client or company ID. This will ensure the desired channel will be found.

• Triggers: We recommend always running the trigger by itself first in order to test the trigger. This will also make the actual output of the trigger available to be mapped to subsequent steps.

• Files: When using the Create a File module in Make, you will want to be sure you have the file binary data available from a previous module. For example, Download a File from Google Drive will return the file binary data needed to map to the Copilot Create a File step.

• Monday.com: The trigger we’ve found best to use is the Watch Events trigger. Follow the Make documentation for Monday to learn how to set up scenarios using Monday modules.