React to GitHub events, set up from your AI assistant
Ask for what should happen when an issue is opened, a pull request is merged or a release is published. ClickRuntime gives you the webhook URL, checks GitHub's signature and runs the code.
- When
- Each incoming event
- Uses
- GitHub
- 08:12✓ Label new issues in acme/app · SucceededLast run08:12 · labelled bug
Can ChatGPT or Claude react to GitHub events?
An assistant can read a repo while you chat, but it can't be notified when an issue is opened. With ClickRuntime connected, it creates an automation with a trigger link that you add as a GitHub webhook. GitHub posts each event there, ClickRuntime checks the X-Hub-Signature-256 header, and the script labels, comments, notifies or updates whatever you asked for.
Why the assistant can’t do this on its own
- GitHub webhooks need a public HTTPS URL that's always up. Assistants don't have one.
- The script needs a GitHub token kept outside the chat. ClickRuntime stores it as a secret.
- Actions workflows can react to events too, but they live in the repo and need YAML. Here you describe the result and it runs across repos without editing any of them.
Set it up from your AI assistant
The same steps work in ChatGPT, Claude, Cursor and any assistant that supports MCP connectors.
- Step 1Connect ClickRuntime to your assistantAdd ClickRuntime as a connector (MCP server) in ChatGPT, Claude, Cursor or another MCP client, using https://clickruntime.com/api/mcp. You sign in with Google or email; there is no API key to copy. This is done once per assistant.
- Step 2Paste the promptStart a new chat and paste: “Create a ClickRuntime automation: when a new issue is opened in acme/app, read the title and body and add one label: bug, feature or question. Check GitHub's webhook signature.” Change the details (times, channels, addresses) to yours.
- Step 3Read the draftThe assistant restates what will happen, asks for anything missing, such as your timezone or which channel to post to, and saves a draft automation. A draft never runs on its own, so nothing happens until you agree.
- Step 4Connect accounts and save keysThe assistant asks you to save a fine-grained GitHub token with Issues read and write on the repo as GITHUB_TOKEN in the ClickRuntime dashboard. It can register the webhook for you with that token, or give you the trigger link and a secret to add under the repo's Settings → Webhooks (content type JSON, Issues events).
- Step 5Test itGitHub sends a ping when the webhook is added; then open a test issue. The assistant checks the stored event, the signature result and that the label was added.
- Step 6Turn it onThe assistant tells you what will run, when, and which services it will contact, then asks your permission to turn it on. From then on it runs on ClickRuntime's servers, and you can close the chat.
- Step 7Check it in the ClickRuntime dashboardIncoming events are listed with the GitHub event type, the signature result and the run each started. The run log shows which label was chosen for which issue. Failed runs can be replayed after a fix.
“Create a ClickRuntime automation: when a new issue is opened in acme/app, read the title and body and add one label: bug, feature or question. Check GitHub's webhook signature.”
Connector setup for each assistant: ChatGPT, Claude, Claude Code, Cursor, and other assistants.
What the assistant writes
A typical script for this job. Yours matches your pages, accounts and wording, and you can read every version in the ClickRuntime dashboard.
- The trigger link's GitHub signature check runs before the script, so `event.is_verified` is true only for genuine GitHub deliveries.
- AI picks the label from the issue text. If AI is unavailable, a keyword rule keeps the run working.
- The same pattern works for pull_request, release, push or star events: the assistant changes the event filter and what the script does.
Trigger link, not a schedule
Use the trigger link for anything that should happen right after a GitHub event.
Use a schedule for checks GitHub doesn't send events for, such as pull requests with no review for three days.
Limits
- Each delivery is one run; subscribe the webhook only to the events you need.
- The GitHub token's permissions limit what the script can do. Use a fine-grained token scoped to the repos involved.
- The AI reads text only; images in issues are not sent.
Troubleshooting
GitHub shows the ping failed.
Check the payload URL is the trigger link and the content type is application/json. The ClickRuntime dashboard lists every delivery that arrived.
Labels aren't added (403 or 404).
The token can't write issues on that repo. Create a fine-grained token with Issues read and write on it and save it again as GITHUB_TOKEN.
Signature checks fail.
The secret in GitHub's webhook settings differs from the one in the trigger link settings. Set the same value in both and redeliver from GitHub.
What you can add next
The first version is rarely the last. Because the automation is a Python script with memory, AI and any API available, you grow it by asking your assistant for the change. Each change is a new version, and a failed deploy never replaces the working one.
- Built-in AI
Comment asking for missing steps to reproduce on bug reports
“Change my issue labelling automation so that when a bug report has no steps to reproduce, it comments asking for them politely.”
- Any app or API
Post new bugs to #engineering in Slack
“Add to my issue labelling automation: when an issue is labelled bug, post its title and link to #engineering in Slack.”
- Any app or API
Copy bugs to Linear with the same title and link
“Add to my issue labelling automation: create a Linear issue in the Platform team for each new bug, linking back to GitHub.”
- Memory between runs
Spot repeat reports by remembering recent issue titles
“Change my issue labelling automation so it remembers the last 200 issue titles and comments with a link when a new issue looks like a repeat.”
- Schedules
A Monday digest of last week's issues by label
“Add to my issue labelling automation: every Monday at 9, email me how many issues were opened last week per label, with links to the bugs.”
- Multi-step logic
Handle pull requests too: welcome first-time contributors
“Change my issue labelling automation so it also handles new pull requests, and comments a thank-you on a contributor's first pull request.”
- Trigger links
Listen to several repos through the same trigger link
“Change my issue labelling automation so it works for acme/app, acme/api and acme/docs, using a different label set for docs.”
Questions about react to github events
Can ChatGPT respond to GitHub webhooks?
With ClickRuntime connected, yes. ChatGPT sets up the automation and its trigger link; GitHub sends events there and the script runs on ClickRuntime's servers.
How is this different from GitHub Actions?
Actions run inside one repo from YAML files. A ClickRuntime automation is described in chat, can span repos and other apps, keeps state between runs and has built-in AI. For CI and builds, Actions is the better fit.
Is GitHub's signature checked?
Yes. Set the webhook secret in the trigger link's signature settings and only deliveries signed with it reach the script.
Can it register the webhook for me?
Yes, when you've saved a GitHub token with permission to manage the repo's webhooks. Otherwise the assistant gives you the URL and secret to add yourself.
Does it work with GitHub organisations?
Yes. An organisation webhook sends events from all its repos to one trigger link, and the script reads the repository from each event.
Other use cases
Scheduled tasks in ChatGPT and Claude
“Create a ClickRuntime automation: every weekday at 9, fetch yesterday's orders from our Shopify store and post the total to #sales in Slack.”
See the use case →Run code every hour
“Create a ClickRuntime automation: every hour, check our public API's /health endpoint and Slack #alerts if it returns anything but 200.”
See the use case →Webhook automation
“Create a ClickRuntime automation: when someone submits our Typeform, add their answers to a message in #leads.”
See the use case →Cron jobs without a server
“Create a ClickRuntime automation: every night at 2am UTC, call POST https://api.example.com/tasks/reindex with my ADMIN_TOKEN and email me if it doesn't return 200.”
See the use case →AI agent automations
“Create a ClickRuntime automation: every morning at 8, summarize new GitHub issues labelled 'bug' on our repo and post them to #eng.”
See the use case →Monitoring and alerts
“Create a ClickRuntime automation: every 5 minutes, check https://api.example.com/health and Slack #oncall if it fails twice in a row.”
See the use case →Stateful automations
“Create a ClickRuntime automation: every hour, check this product page and email me only when the price drops below the lowest price you've seen.”
See the use case →AI triage and summaries
“Create a ClickRuntime automation: every 15 minutes, label new support emails as billing, bug or other and post billing ones to #billing.”
See the use case →Website change alerts
“Create a ClickRuntime automation: every hour, check https://acme.com/pricing. Only look at the pricing table, not the whole page. When it changes, email me a short summary of what changed. Don't email me when nothing changed.”
See the use case →Price drop alerts
“Create a ClickRuntime automation: every 2 hours, check the price on https://shop.example.com/products/monitor-27. Email me when it drops below $280. Tell me only once per drop, and include the lowest price seen so far.”
See the use case →Uptime checks
“Create a ClickRuntime automation: every 5 minutes, check https://app.example.com/health. It's down if the status isn't 200, it takes longer than 5 seconds, or the body doesn't contain "ok". After 2 failures in a row post to #ops in Slack, and post again when it's back up with how long it was down.”
See the use case →RSS feed alerts
“Create a ClickRuntime automation: every 30 minutes, check https://www.postgresql.org/news.rss. Post each new item to #eng in Slack with its title, link and a one-line summary. Never post the same item twice. On the first run, don't post old items.”
See the use case →Job post alerts
“Create a ClickRuntime automation: every 2 hours, check the Greenhouse job boards for the companies acme and betaco. Email me new jobs that are product design roles open to remote work in Europe. Include title, location and link. Never send the same job twice.”
See the use case →Brand mention alerts
“Create a ClickRuntime automation: every 30 minutes, search Reddit and Hacker News for "Acme CRM". Post each new mention to #mentions in Slack with the title, link and a label: question, complaint, praise or other. Never post the same thread twice.”
See the use case →Daily Slack message
“Create a ClickRuntime automation: every weekday at 9:00 Europe/Berlin, post to #team in Slack: a good-morning line, the number of open issues labelled Bug in our Linear team ENG, and the 3 oldest ones with links.”
See the use case →Daily news digest
“Create a ClickRuntime automation: every day at 7:30 Europe/London, collect new items from these feeds: <feed URLs>. Pick the 5 most important for someone following AI policy in the EU, and email me a digest with a two-sentence summary and link for each. Don't include anything I was sent before.”
See the use case →Weekly metrics to Google Sheets
“Create a ClickRuntime automation: every Monday at 7:00 America/New_York, add a row to the KPIs tab of my sheet “Company metrics” with the week start date, last week's Stripe revenue (succeeded charges minus refunds), number of new customers and number of refunds.”
See the use case →Morning briefing
“Create a ClickRuntime automation: every weekday at 7:00 Europe/Lisbon, read today's events from my work Google Calendar, get today's forecast for Lisbon, and email me a short briefing: the weather in one line, each meeting with time and who's in it, what I should prepare, and my free blocks of 30 minutes or more.”
See the use case →Slack channel summary
“Create a ClickRuntime automation: every weekday at 17:30 America/Chicago, read today's messages and thread replies in #product, and post to #product-digest a summary with three parts: decisions made, open questions, and action items with who owns them.”
See the use case →Inbox summary each morning
“Create a ClickRuntime automation: every weekday at 7:30 America/Los_Angeles, read the emails that arrived in my Gmail inbox since the last summary. Email me a summary in three groups: needs a reply, FYI, and newsletters or notifications. One line per email with the sender. Skip anything I already read.”
See the use case →Form submissions to Google Sheets
“Create a ClickRuntime automation: when someone submits my Typeform contact form, add a row to the Leads tab of my Leads spreadsheet with the date, name, email, company and message. Check the Typeform signature so only real submissions are added.”
See the use case →Form leads to your CRM
“Create a ClickRuntime automation: when my website form posts a lead (name, email, company, message), create or update the contact in HubSpot by email, set lifecycle stage to lead, and add the message as a note on the contact.”
See the use case →Handle Stripe webhooks
“Create a ClickRuntime automation: when Stripe sends checkout.session.completed, post the customer email and amount to #sales in Slack. Check the Stripe signature and handle each event only once.”
See the use case →Sort Gmail automatically
“Create a ClickRuntime automation: every 15 minutes, look at new messages in my Gmail inbox and add one label: Invoice, Customer, Newsletter or Needs reply. Email me straight away when a customer message sounds urgent.”
See the use case →Recurring reminders
“Create a ClickRuntime automation: on the last weekday of every month at 10:00 London time, post “Reminder: send this month's invoices” to #finance in Slack.”
See the use case →Stale pull request reminders
“Create a ClickRuntime automation: every weekday at 9:30 Berlin time, find pull requests in acme/app and acme/api that are not drafts, have been open more than 24 hours and have no review yet. Post them to #eng in Slack with the title, age, author and requested reviewers. Post nothing if there are none.”
See the use case →Scheduled social posts
“Create a ClickRuntime automation: every 15 minutes, read my Post queue sheet (columns: When, Text, Status). Publish each row whose When has passed and whose Status is empty to my LinkedIn profile, then set Status to the post link.”
See the use case →Sync data between apps
“Create a ClickRuntime automation: every 30 minutes, find records in my Airtable Customers table that changed since the last run, and create or update the HubSpot contact with the same email, copying name, company and plan.”
See the use case →Summarise customer feedback
“Create a ClickRuntime automation: every Monday at 9:00, read the rows added to my Feedback sheet since last time (columns: Date, Source, Text), group them into up to 6 themes with a count and one short quote each, and post it to #product in Slack.”
See the use case →Daily standup in Slack
“Create a ClickRuntime automation for our async standup: every weekday at 9:30 Berlin time, post “Standup: what did you do yesterday, what's next, anything blocking?” in #team. At 12:00, read the replies in that thread and post a short summary in the thread, listing blockers first and who hasn't replied.”
See the use case →
Set up your first automation in ChatGPT or Claude
Free plan. No credit card.