Should zapier updates trigger workflows?

I have a zapier automation triggering a single select field update when an invoice is paid. I also have a workflow that creates a status notification record when the select select field is updated. The workflow functions fine for edits within noloco but is not triggered when updated by zapier.

Is this expected or a error?

I think this is expected behaviour, changes made via API (including making changes directly in an external data source (e.g. Airtable)) don’t seem to trigger Noloco workflow.

1 Like

It depends on how you are making the change with Zapier. I have a workflow setup that is triggered when Zapier makes a change to a record and it works for me.

Hi, @thecasemaster can you elaborate on your solution so that maybe we can benefit from it? Thx.

For sure! So in my use case, I use Airtable as my back end. A few of my users are on the Airtable side and the rest are on the Noloco side. I’ve built out an activity log and needed a way to send push notifications to my Noloco users via the app when users on the Airtable side log a new activity log entry. Basically I have an automation in Airtable that logs the new log entry when a button in an interface is pushed. Behind the scenes, there is a check box for the sole purpose of triggering Noloco and a “last updated” field that only watches for changes to this checkbox. When the automation in Airtable runs the new log entry, it checks the checkbox. I have a view in Airtable that filters records based on if that checkbox is checked. Then Zapier watches this view and when updated records, based on that “last modified” field watching that checkbox, enter the view, Zapier updates the same record in Noloco and unchecks the box. Then on the Noloco side I have a workflow that is watching this same checkbox field and will run when the field is updated. So the Zapier zap that unchecks the box in Noloco triggers the Noloco side to run and then my Noloco users receive their notifications. Since the checkbox isn’t checked anymore, it filters out of the view in Airtable that Zapier watches so that when one of my Airtable users adds subsequent activity logs, it will go back into that filtered view, then retrigger Zapier, and thus Noloco all over again.

1 Like