Connect Eggtimer to Zapier
Start a timer from a Zap.
Run another step when a timer or routine stage finishes.
The native Eggtimer integration is a private beta, version 0.1.0. It is available through the invitation below; it is not a public App Directory listing. Your workspace key controls only your workspace.
1. Save your workspace keys
Create a free workspace. Save its private credential file. Your API key begins ew_; your separate recovery key begins er_. Keep the recovery key out of Zapier.
2. Connect Eggtimer
Accept the invitation in Zapier. Choose Eggtimer.app, select an event, and connect using the workspace API key. This lets Zapier create, inspect and cancel timers and routines in that workspace. Replace the key in Eggtimer to revoke the connection; reconnect authorized clients afterward.
3. Choose an action or trigger
| Operation | Use it for |
|---|---|
| Start Timer | A duration from one second to 30 days. |
| Start Timer Until a Date | A future instant with an explicit timezone offset. |
| Start Routine | Recipe JSON with whole-second steps, cycles and automatic advancement. |
| Find / Cancel Timer or Routine | Read state or stop outstanding work using the returned ID. |
| Create Timer Link / Routine Link | Generate a URL for a person. These actions do not schedule a server job. |
| Timer Finished | React to a completed one-shot timer. |
| Routine Progress | React to step starts/finishes, cycle finishes, or whole-run transitions. |
Give each intended run its own request key
Map a stable unique ID from the trigger and add a suffix for this action. Use 10–80 letters, digits, hyphens or underscores. Retries reuse the key; a new intended timer requires a new one. A constant value would return the original run instead of starting a new timer every time.
Example: act after each work/break stage
Create a recipe with Focus (1,500 seconds), Break (300 seconds), four cycles and automatic advancement. In another Zap, use Routine Progress → Step finished, then filter by the phase label if only a break or work stage should trigger an action. The event includes the routine ID, phase label, cycle, original scheduled time and a link to that step.
The native triggers poll at the interval supplied by your Zapier plan. They are not instant. Routine history retains at most 1,000 events and seven days; one-shot polling uses up to 100 recent timer records. A long pause can miss expired records. Stable event IDs identify each transition; receipt updates do not create a new event.
Direct Catch Hooks are a separate option
If you want Eggtimer to POST a selected event directly, privately enter a Zapier Catch Hook in the workspace or API request. Each routine event has an independent outbox, up to three attempts by default and a five-minute freshness window. This delivery does not wait for a native polling interval, but it can still be late, duplicated, reordered or fail. A successful HTTP response does not prove later Zap actions succeeded.
Routine event and delivery contract · Browser Catch Hook setup
Limits, plans and support
The Eggtimer beta includes 50 new timer/routine runs per workspace per UTC day, ten active slots, 500 reserved routine events/day and shared deployment caps. Zapier's plan eligibility, polling intervals and task usage apply separately. No credit card is required by Eggtimer. Full limits and retention.
Questions: support@eggtimer.app. Never send your keys or hook URL in a support message.