fix: clarify Zapier webhook path #29304
Merged
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
PR Summary
This PR clarifies the Zapier webhook path documentation in the template configuration, making it easier for users to correctly set up the Zapier integration.
- Updated description in
posthog/cdp/templates/zapier/template_zapier.pyto specify that users should enter the path after "https://hooks.zapier.com/" with a clear example format (hooks/catch/12345678/2gygaul/) - Added reference to the native Zapier integration as an alternative option (https://zapier.com/apps/posthog/integrations)
1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
meikelmosby
approved these changes
Feb 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
It was unclear which part of the Zapier webhook URL should be used in the destination.
Changes
Adds a comment specifying the format.
Cherry-picked from #29073, to streamlined the deployment.
👉 Stay up-to-date with PostHog coding conventions for a smoother review.
Does this work well for both Cloud and self-hosted?
Yes
How did you test this code?
Only a documentation change.