Server timers
Start a timer here or through the API. It can call Zapier when it finishes, even after you close the page.
Free plan. No email or payment required.
Zapier calls this an account. You’re connecting an Eggtimer workspace: a private place for your timers. You don’t need an Eggtimer email address or password.
Get a key here, copy it, then paste it into the Zapier window.
Create a workspace
We’ll give you an API key and a separate recovery key. Save them somewhere private. No password, inbox or credit card required.
50 new timers or routines a day · 10 active at once · up to 30 days each · 500 routine events a day.
A shared free-plan allowance also applies. Delivery is best effort.
Already have a workspace?
2. Copy your connection key
Your key is ready. It lets Zapier start, check and cancel timers in this workspace. Keep it private.
Copy the key to continue.
3. Finish in Zapier
Return to the Zapier window. Paste the key into Eggtimer connection key, then click Connect.
No Zapier window open? Add Eggtimer to Zapier, choose an event and connect.
This file lets you reopen your workspace. Keep it and your recovery key private. Use only the connection key in Zapier.
Your workspace
Your keys and AI connection
Keys stay in this page’s memory. Save the credential file before closing. Anyone with the API key can manage this workspace’s timers; the recovery key can replace that key or shut the workspace down.
Connect a header-capable MCP client to https://eggtimer.app/api/mcp/server with your API key in its Bearer header.
AI client setup and limits ↗ · HTTP API and Zapier guide ↗
Email recovery is not configured yet. Save the recovery key; we cannot retrieve lost keys.
Schedule a timer
Run a routine
A sequence of timed steps, with a separate event at each transition. The schedule runs on our servers.
Your routines
Your timers
Server status is checked on request. Closing this page does not stop your timers.
Replace a key or close the workspace
Paste your saved recovery key above. Replacing the API key disconnects clients using the old one; existing timers continue. Closing the workspace stops future delivery attempts and cancels pending timers. Already sent or in-flight webhooks cannot be recalled.