Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Eligible Plus, Pro, Business, Enterprise, Edu, and Healthcare users can create Gmail, Slack, and GitHub event-triggered tasks in ChatGPT Work. Free, Go, and FedRAMP workspaces cannot create them.
- Free, Go, Plus, and Pro can share scheduled tasks, but recipients create copies they can modify, connect to their own apps, and run independently. They do not take over the original task or its account permissions.
- Ordinary scheduled tasks run at a time or interval; event-triggered tasks wait for changes in supported apps. If an older help page says webhooks are unsupported, use the August 25 update and Work eligibility as the reference, while confirming that you are in the corresponding product interface.
- Connecting an app does not authorize every action. Reads, writes, administrator policies, and actions requiring human approval remain governed by app authorization and workspace settings.
- Use a test event without side effects to verify triggering, deduplication, approvals, and notifications before connecting workflows that modify external systems. Pause if tasks trigger repeatedly, target the wrong channel, or lack an approval owner.
What changed: schedules work, but app changes do not trigger a run
On August 25, 2026, OpenAI announced that Scheduled tasks in ChatGPT Work can respond to new Gmail messages, new Slack channel messages, and GitHub pull request activity. The help page updated on August 27 describes eligibility more fully: eligible Plus, Pro, Business, Enterprise, Edu, and ChatGPT for Healthcare users can create them; Free, Go, and FedRAMP workspaces cannot. No additional regional list is provided, so a missing entry point cannot immediately be attributed to an IP or proxy issue.
A typical scenario is a team wanting a checklist automatically generated after a PR update. Its daily 9 a.m. task runs, but PR changes do nothing. The visible symptoms are no new run records or a task waiting at app connection or approval. The cost is missed delivery milestones and repeated manual checks. The wrong instinct is to keep shortening the schedule interval. First confirm that the task was created in ChatGPT Work as a supported webhook task, then check the plan and app connection.
Old and new approaches: distinguish time triggers, monitoring, and webhooks
Time triggers suit daily, weekly, or specific-window execution. Monitoring tasks periodically check for changes. New webhook tasks start from supported app events. These have different trigger sources. If the requirement is to process a specific email immediately on arrival, daily polling introduces delay. If the requirement is only a morning briefing, an event trigger can cause excessive runs.
Older Scheduled Tasks help content may still say ordinary tasks do not support webhooks, while updated guidance explicitly limits event triggers to ChatGPT Work, eligible plans, and supported apps. When troubleshooting, record the help page's update date, product entry point, plan, workspace, and client together. Do not combine old snapshots and current rules into a contradictory description of the product.
Eligibility and permission checks before creation
Confirm five things first: the account has an eligible plan; you are using Work; Gmail, Slack, or GitHub is connected; the source-system account can read the target resource; and administrator policy allows event triggers. Enterprise, Edu, and Healthcare administrators must enable Allow event-triggered scheduled tasks. Healthcare defaults to off, and event-triggered tasks are not covered by the BAA and must not transmit, store, or process PHI. Slack also requires @ChatGPT to be added to every monitored channel.
Apply least privilege when checking app permissions: begin with read-only access to one test mailbox label, channel, or repository. The web and supported mobile clients can create, share, and update event-triggered tasks. Desktop can display existing tasks but cannot create or edit trigger conditions. App permissions do not bypass existing Gmail, Slack, or GitHub permissions, and sharing a task does not transfer the creator's authorization to recipients.
A minimal validation workflow for the three trigger types
For Gmail, send a new message with a dedicated test subject and confirm the task reads only the expected mailbox scope. For Slack, add @ChatGPT to a test channel, then send a uniquely marked message. For GitHub, change a test PR title or submit one harmless change. Produce only one event at a time, recording the event time, task run time, input source, and output destination.
Validation should cover at least one success, one duplicate event, one permission failure, and one action requiring approval. All event-triggered tasks together are limited to 30 runs per hour and 720 per day, and multiple events may be combined. Do not continue load testing through repeated events when limits are reached or traffic surges. If one event causes two external writes, pause the task and check idempotency keys. If it sees content it should not access, immediately disconnect the app and have an administrator review the authorization scope.
Sharing a task does not share an account, connection, or run history
Eligible users can share scheduled tasks. A shared link exposes the title, instructions, schedule, and original time zone, but does not include chat history, memories, attachments, connector data, or credentials. Links created by personal accounts can be viewed by anyone who has them. Recipients create copies they can edit, connect to their own apps, and run independently. They do not automatically receive access to the sender's mailbox, channels, or repositories.
To run a shared event-triggered task, recipients still need Work access, an eligible plan, and their own app connections. Remove client names, internal URLs, secret values, and unnecessary resource identifiers before sharing. Scheduled tasks themselves are included in the Compliance API, but shared links and their saved snapshots are currently outside that coverage. Regulated teams should include this difference in approval reviews.
Approvals, failures, and stop conditions
Actions requiring approval pause until the user reviews them. For external writes such as sending messages, changing issues, or submitting forms, define who approves, the maximum wait, and whether a timeout should only notify without executing. Do not immediately treat an unfinished task as a network failure. First inspect run records, connection status, administrator policies, and the approval queue.
Stop conditions include an unbounded trigger scope, repeated execution of the same event, unclear approval responsibility, recipients mistakenly believing they inherited the original account's permissions, writes to the wrong channel or repository, and uncertainty over whether data can be shared. Pause the task, retain event and run evidence, and first switch to read-only summaries or human confirmation.
Common misconceptions and troubleshooting order
Common misconceptions include assuming that Free's ability to share tasks means it can create webhooks; connecting an app authorizes all actions; a missing entry point on the ordinary Scheduled page proves regional blocking; task sharing includes the original connection; or unlimited retries can solve repeated triggers. The correct order is product interface and plan, task type, app connection, source-system permissions, approvals, trigger event, deduplication, and only then DNS, TLS, or proxy authentication.
If only ChatGPT cannot connect to an app, consult IP and browser checks before login and the proxy connection troubleshooting checklist. Network egress only affects the connection path. It cannot add Work access, change administrator policies, or turn unsupported events into webhooks.
Pre-rollout checklist and review timing
Confirm each item: primary account and workspace eligibility are correct; the administrator switch is enabled; the task was created in Work; app connections and least privilege have been reviewed; @ChatGPT is in the Slack channel; a test event triggers only once; the 30/720 run boundaries are monitored; writes receive suitable approval; the shared snapshot contains no sensitive configuration; recipients have tested with their own connections; and pause and deletion owners are identified.
OpenAI may continue adjusting plans, clients, and supported apps. Review duplicate triggers and approval backlogs 24 hours after the initial rollout. After one week, recheck the official Release Notes and Scheduled Tasks help page. If they still differ, use the more recently updated official explanation that directly matches the current product scope as the factual boundary.
Sources
Frequently Asked Questions
Which accounts can create Gmail, Slack, and GitHub event-triggered tasks?
Eligible Plus, Pro, Business, Enterprise, Edu, and ChatGPT for Healthcare users can create them in Work. Free, Go, and FedRAMP workspaces cannot. Enterprise, Edu, and Healthcare also require the administrator to enable the relevant switch.
Can Free or Go use webhook tasks?
They cannot create webhook-triggered tasks. Free and Go can share or receive eligible scheduled tasks, but event triggers still require the recipient to have Work access and their own app connections.
How often can event-triggered tasks run?
The official combined limit for all event-triggered tasks is 30 runs per hour and 720 per day. Multiple events may be combined. At the limit, pause high-frequency sources and inspect trigger conditions rather than blindly retrying with duplicate events.
Does sharing a task give someone my Gmail or GitHub permissions?
No. Recipients create independent copies and connect their own apps. Source-system and workspace permissions still apply. Remove sensitive information from instructions before sharing.
Why did a Slack message not trigger the task?
First check the task type, plan, and app connection. Then confirm that @ChatGPT has joined the target channel, the account can read it, and no pending approval or administrator restriction is blocking execution.
When should an event-triggered task be paused?
Pause immediately for duplicate external writes, incorrect destinations, unclear permission scope, missing approval ownership, or shared sensitive configuration. Switch to read-only or human confirmation, and resume only when the evidence is complete.