TempoLife › Features › Automations and webhooks › ifttt

IFTTT

There is no TempoLife app on IFTTT. Here is the generic incoming-webhook route that will work when TempoLife deliveries start, written out step by step.

No TempoLife service publishedSignature: HMAC-SHA256Checked 2026-09-02

No deliveries are being sent. The delivery worker is not built, so a webhook registered today records your URL, your event and your signing secret and then sits there — TempoLife makes no outbound request to it, not even a test ping. Registering now is only worth doing if you want the secret ahead of time so you can write and unit-test your verification code. Deliveries begin when the worker ships.

The honest status

There is no TempoLife app, module or service on IFTTT. Searching their directory will find nothing, and nobody is publishing one this week. What each of these platforms does offer is a generic way to receive an HTTP request, and that is the route TempoLife webhooks will take when the delivery worker ships.

Being blunt about that is more useful than a "coming soon" badge: a published platform app means certification, a maintained OAuth integration and a support commitment. Until the underlying webhook delivery exists there is nothing to certify, so the generic route is not a workaround — it is the design.

Setting it up, step by step

1. Add the Webhooks service to your IFTTT account. It is IFTTT's own service for arbitrary HTTP, and it is how anything without a published service gets in.
2. Note the direction carefully. IFTTT Webhooks is strongest at <em>making</em> requests. Receiving one requires the "Receive a web request" trigger, which expects IFTTT's own URL shape and its own key in the path.
3. Understand the limitation before you build. That trigger accepts up to three loose values and does not expose the raw request body to your applet. You therefore cannot verify a TempoLife signature inside IFTTT — the bytes it was computed over are not available to you.
4. Decide whether that is acceptable. For a low-stakes applet — a light that changes colour when a step goal is hit — an unverified trigger may be fine. For anything touching health data or a permanent record, put a small endpoint of your own in front and let it verify, then call IFTTT.
5. Register the URL here once you have chosen. The registration form accepts IFTTT's https URLs.

Every one of those steps can be completed today except the last thing that matters: a delivery arriving. Your scenario will sit waiting until the worker ships.

What it costs you

Each platform bills per task or per operation, and the trigger volumes on the automations page are the numbers to plan against. meal.logged is the expensive one at three to six a day per user; weight.updated and steps.goal_reached are at most one a day each. If you are building for yourself, start with a quiet event and add the noisy one once the scenario is proven — it is much cheaper to discover a bug at one task a day than at six.

When a raw webhook is the better answer

If you already run a server, skip the platform. A verified receiver is about thirty lines, it costs nothing per event, the health data never passes through a third party, and you get the raw body the signature was computed over. The raw webhooks page has a complete receiver you can paste.

Register the URL now if you like

Registration is open and free, and it hands you the signing secret you will need for the verification step above. Nothing will arrive at it yet.

Register a webhookDo it without a platform

Frequently asked questions

Source: TempoLife platform specification — event, signature and retry policy · checked 2026-09-02

Other platforms

Payloads, signing and the retry policy · Developer API