How to prevent repeating back-and-forth Zaps?

Hi @Henrik 

Zapier is not meant to 2-way syncing of data: https://zapier.com/help/create/basics/does-zapier-support-two-way-syncing

If you can add a reference ID (e.g. record ID) from each app into the other app, then you may be able to filter based on whether that reference ID exists, in order to prevent the infinite loop and errors.

Otherwise, try implementing this type of logic: find record else create record, then update record.

Thank you @Troy Tessalone for the suggestions, your idea for implementing the final logic did work well for my Zaps that involved creating a new record in Adalo, triggering a new row in MySQL. However, on the flip side, creating a new row in MySQL to trigger a new record in Adalo cannot have this type of logic implemented so easily. 

The issue is actions for MySQL include creating, updating, and finding rows in a table. But Adalo only has creating and updating records as available actions. I have been trying to work with both your suggestions on these more problematic Zaps, but unfortunately have still not been able to cease the issue of the following loop: New record in Adalo → new row in MySQL → New (Duplicate) row in Adalo. 

Is there a way to implement a ‘find record’ action for Adalo in Zapier? Any advice is greatly appreciated.

Thank you @Troy Tessalone, I’ll dive into these APIs and get back with updates

Hi @Troy Tessalone, I believe I almost have it but am experiencing one small hiccup.

The Webhook step works well after I pulled the GET URL and Content-Type & Authorization headers from the Adalo API documentation of my database. My issue is the test is getting the wrong single record from my ‘groups’ table.

I am trying to specify that a record in Adalo should be searched for by matching the Group ID from MYSQL under the Query String Params (I’m not certain if Query String Params is the correct way to specify which column to search by). However, every test result both from running the in-Zap test (2nd screenshot) and creating a new row in MySQL and reviewing the zap runs (final screenshot) show the same results: Group_id 2 is always being read from MySQL, no matter the new row I create.

Many thanks again for your help with this so far

@Henrikcox 

Can you indicate which Adalo API endpoint documentation you are referencing by linking to it?

That would be the documentation page found when clicking the three dots next to a database collection, and the ‘Fetch a single collection record’ endpoint

@Henrikcox 

This Adalo API endpoint expects 3 path parameters and 0 Query String Parameters.

NOTE: I don’t see documentation in the screenshot related to “group_id”, which may explain why the returned results are not what you are expecting.

Would need to see more screenshots with how your Zap step is configured for the full API request.

@Troy Tessalone 

I’ve attached screenshots of the full Zap step, including the review test in progress and results. I’m not sure where the path parameters can be inputted, and replace those with the current query string parameters

@Henrikcox 

Path parameter are part of the URL, which should be indicated by the Adalo API documentation:

You may have to use a different endpoint then filter those results by your query criteria:

@Troy Tessalone 

I’ll give that a go! I also tried replacing the end of the Endpoint URL with {ElementId} instead of 1 and feeding in the group_id through the query string parameter but had a bad request. I’ll try getting all collection records and filtering through that way.

@Henrikcox 

Keep in mind that the Path parameters for Adalo API are going to expect internal Adalo IDs for the appID, collectionID, and elementID.

That worked great! I went with the endpoint of getting all the collection records, and then changing the next filter step to the following:

Thank you so much @Troy Tessalone, your advice was incredibly healpful!