Add Zapier trigger that fires when Documents are updated #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@tommoor I haven't tested this yet — just wondering if you'd be interested in a PR like this before I spend more time on it.
This is just a copy of the original
document
trigger with a synthetic compoundid
that includes the document'srevision
as a suffix. The Zapier docs on "update triggers" are a bit bare but I believe this is how it works.My one concern is that if a single Document is updated multiple times (i.e. multiple Revisions are created) in quick succession (i.e. within the polling interval), the Zap will trigger once for each of them. I suppose this is intended behavior on the Zapier platform.