Tasks triggered by events in ChatGPT

Create a task that responds to a supported app event instead of checking on a timer. This feature runs in ChatGPT on the web or mobile; it is not available in the Codex desktop app, CLI, or IDE extension. The example produces a private summary when a website pull request is merged.

Before you start

• ChatGPT on the web or mobile with event-triggered tasks enabled for your plan and workspace. In managed workspaces, an administrator controls the Allow event-triggered scheduled tasks permission.
• A connected and authorized GitHub app with access to the repository you want to watch.
• A repository and pull request you are allowed to use for a test. Prefer a harmless documentation change that can follow your normal review process.
• A sample pull request URL and a clear output format. This walkthrough summarizes existing changes; it does not ask ChatGPT to modify code.

Want to do it yourself?

Difficulty

8 out of 10

Estimated completion time

1–2 hours, plus waiting for a test event

Skills you’ll need: Configure an event trigger, check permissions and inputs, and verify that one real event produces the intended result.

I’ll do it myselfI’d rather get help

How this helps your brand

A checked summary of merged website changes can help you decide what to verify for visitors next. Narrow event filters and source links keep that follow-up connected to real repository activity.

1. 1

   Step 1: Define one event and one useful result

   Choose a narrow event, such as a merged pull request in your website repository. Ask for a short private summary with the pull request link, visitor-facing changes, and checks you should perform.

   Keep the trigger separate from the task’s instructions. The trigger decides when it runs; the saved prompt decides what it does. A task can have multiple event triggers, but cannot combine event triggers with a time-based schedule.

2. 2

   Step 2: Confirm the connection and supported event

   Open ChatGPT on the web or mobile and connect and authorize GitHub for the intended repository. Ask ChatGPT to confirm it can read the sample pull request before creating the trigger.

   GitHub triggers support pull request activity, with filters for pull request, author, title, or label, and choices for reviews, comments, commit updates, or merges. Select only merges for this example.

   Other supported sources include incoming Gmail messages and messages in selected Slack channels. Slack reactions, edits, deletes, and direct messages are not supported; a Slack task also needs @ChatGPT added to each watched channel.

   Illustrated exampleLet only the intended event through

   Example repositorynorthline/website

   Read access confirmed

   Incoming pull request activity

   • MergedPasses
   • Comment or reviewExcluded
   • Commit update aloneExcluded

   Merge event only

   Private summaryIn ChatGPT on web or mobileNo time-based schedule

   Trigger · when

   A pull request merges in this repository.

   Saved prompt · what

   Read the merged PR. Summarize visitor changes, check results and three things to verify. Identify unknowns.

3. 3

   Step 3: Try the summary before saving the trigger

   In a regular chat, give ChatGPT the sample pull request and the desired instructions. Ask it to read the source and produce the proposed summary without creating an ongoing task yet.

   Check the link and compare every claim with the pull request. If a check result or visitor effect is unclear, the summary should say so. Refine the instructions until this one-off output is useful.

4. 4

   Step 4: Create and inspect the event task

   Send the prompt below, with the repository and merge event filled in. Ask ChatGPT to confirm the saved trigger, repository, output destination, and actions it is allowed to take.

   Open Scheduled and inspect the task’s saved instructions and recent runs. Confirm it watches only the intended repository and merge events. If you are using Codex on desktop, switch to ChatGPT web or mobile for this setup rather than assuming a desktop schedule can receive these events.

5. 5

   Step 5: Test a matching event and a non-match

   Use your normal process to merge an approved, harmless test pull request in the watched repository. Then open Scheduled to inspect the resulting run and output. If matching events are pending, Run now can process them.

   Create or comment on a separate test pull request without merging it. A merge-only task should not run for that activity. Review the recorded events and runs rather than relying only on a notification.

   Several nearby matching events may be combined into one run. Do not expect exactly one message per event or an immediate result.

   Illustrated exampleVerify what starts a run—and what does not

   Illustrative test recordTwo merges. One comment.All in northline/website

   1. 09:10
      PR #42Merged · clarify contact hours
      Matching event
   2. 09:12
      PR #43Comment added · update services
      No run from this event
   3. 09:14
      PR #44Merged · correct service area
      Matching event

   #42#44Matching merges

   One possible resulting runSummary includes both PRsKeep each link and its changes identifiable.

   Inspect recorded events and runs in Scheduled. Nearby matching events may be grouped; timing and run count can vary.

6. 6

   Step 6: Narrow noisy triggers or repair missing access

   If unrelated activity starts runs, check the saved event type and repository filters and ask ChatGPT to correct them. If an intended event is missing, check pending events, repository access, the app’s authorization, and workspace permission.

   Repeat the harmless test after the correction. When the experiment is finished, ask ChatGPT to disable or delete the task and verify its state in Scheduled. Keep a useful task only after both the matching and non-matching cases behave as intended.

Create an event-triggered task in ChatGPT.

Watch this GitHub repository: [owner/repository]
Trigger only when a pull request is merged. Do not trigger on reviews, comments, or commit updates alone. Do not add a time-based schedule.

For each run, read the matching merged pull request or pull requests and give me a private summary in ChatGPT: the original links, what changed for website visitors, the available check results, and three concrete things I should verify. Identify anything the sources do not establish. If multiple events arrive together, keep each pull request identifiable.

Do not edit code, create issues, post comments, merge, push, or deploy. Confirm the saved event filters, connected account access, and where I can inspect runs or disable the task. If event triggers are unavailable for my account, explain the limitation without creating a different kind of task.