The webhook payload is passed as-is to the bottom of whatever prompt you’ve configured for the automation! No special parsing needed.
(This was also a surprise to me, who is used to having to send webhooks is a certain format to do anything with them. Not so with Automations!)
Thanks, I will give this a try. I had a reply from email support and they thought that the webhook payload was not accessible. Are you 100% sure that it does get added to the instructions block? I will try and test it, but it will be a bit time consuming to work out what’s going on.
I’ve got another question, if I may. Why is the set of GitHub actions so limited in the Automation?
It would really help if I could search for issues and have access to other GitHub tools. GitHub is also not available to be added as a MCP integration in the list of available apps.
consider my automation as one that takes care of fixing production errors. I want to avoid the same automation being instantiated multiple times for the same error. So I need to first log an issue and then have the automation check if that issue already exists before it proceeds.
For now I’ll use Pipedream as an intermediary to manage this.
Thanks.
They are definitely added! You can see it yourself in any automations they trigger
Will mention this to the team member you were talking to. 
We have to start somewhere. Thanks for the feedback!
You can always add a custom MCP server if one you see isn’t listed! The configuration will match what you have defined in your local .cursor/.mcp.json.
Facing same issue. Any fix or workaround it yet?
Thank you very much. Apologies, I didn’t want to come across as moaning, but I am struggling getting the right combination of triggers and actions in place. I appreciate the feature set has to be limited to start with.
Maybe you happen to know a vibe coding tool that could help you ship quicker? 
Going to close out this thread since Automations have been out for a little while now. Please keep sending feedback/issues in the appropriate forum category!
