Why is this important?
If your organization uses GitHub to manage software development tasks, then you might find it helpful to have Receptive automatically create issues in GitHub when a Receptive request gets to a certain stage.
Use Receptive as a customer-facing and business-facing tool to manage requests & feed requests into your development tools at the right moment.
In this walkthrough we’ll take a request created by a customer in Receptive, and update it to “Building”. At this point, Receptive will feed it into GitHub as a new Issue.
This method uses Receptive’s Zapier integration. Zapier allows you to connect Receptive to 1000+ apps, without needing code or developer time.
You can use the pre-made template below to easily setup the connection with GitHub, or you carry on reading to do it manually.
How to connect Receptive to GitHub
Firstly you’ll need to create a Receptive API key in your Settings/Integrate page.
Then log into your Zapier account (free tier will work) and click on “Make a Zap”
Choose Receptive as a trigger app.
Choose a trigger action. In this example we’ll fire the Zap whenever a request has its status updated
Slight detour to choose the Receptive account and test the integration is wired up.
We choose to only fire this Zap when a request changes status to “Building”
If you test the step, which is recommended, then Zapier will ask you to update a request to “building” in Receptive now, and wait to receive the event, which should happen within a few seconds.
Choose GitHub as your action app.
Choose “Create Issue” as your GitHub action.
You may have to take a slight detour here to authorise GitHub to talk to Zapier. Then test your GitHub connection and look for the “success” indicator.
Next we set up what your new GitHub issue will look like. We choose a repo and merge in the “title” and “description” from Receptive’s request.
Something we do on our own integration with GitHub is label the incoming GitHub issue as an “Enhancement”
Now Zapier will create the issue in GitHub as a test
You can name the Zap and optionally switch it on for immediate integration, or wait until you are ready.
So to summarise, when a request is updated to “Building”, a new issue in GitHub is automatically created.