Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Is it possible to attach a Slack message, or the contents of the message, to a GitHub issue?

In my workflow, a GitHub issue gets created when a Slack message matching a certain criteria is received. I’d like to be able to better map the GitHub issue to the Slack message.

Hi @gmoney, thanks for joining the Community here! 🎉 

The Slack triggers should provide the text for the Slack message that you can then select in the GitHub action. For example the New Message Posted to Channel trigger supplies the message contents in a field called Text. So if you map that Text field to the Body field on a Create Issue (GitHub) action then the contents of the Slack message will be added to the issue that’s created.

For example:

4d49e2062aff4af29383223dbd5f260b.png

Not sure what criteria you’re wanting to use for determining which Slack messages should be passed to GitHub but, if you’ve not done so already, you may want to look at adding a filter to the Zap to help check for certain conditions. You can learn more about using filters in our Add conditions to Zaps with filters and Filter and path rules in Zaps guides.

Hope that helps to get you pointed in the right direction. If you run into any issues on that or have further questions do let us know!

Thank you @SamB ! Do you know if there’s a way to attach the actual file to the GitHub issue the way it gets attached to the Slack message like in the first pic instead of adding the link to it?

 

Thanks for getting back to me here @gmoney.

Hmm, it doesn’t look like there’s any sort of attachment field available. So I’d recommend reaching out to our Support team to ask that they open up a new feature request on your behalf for the ability to attach files to new issues when creating them. You can do that here: https://zapier.com/app/get-help.

As a workaround, it looks like GitHub supports basic authentication so you could potentially use a Webhooks action to create the issue and add the attachment that way (assuming their API supports the upload of files to issues)? It’s a bit advanced as you’d need to reference GitHub’s API documentation to set up the request and would require a paid plan. But if you’d like to explore that we have a general guide on how to set up Webhooks actions to help get you started: Send webhooks in Zaps

Hope that helps. If you get stuck at all on that do let us know, happy to assist further! 🙂

Terms & Conditions