Make recipe

Track client response time with Make

Two scenarios, one HTTP module each — map your trigger's fields into ReplyTime's webhook body.

1

Create an API key

In ReplyTime, go to Settings → API Keys and create one named after this scenario, e.g. “Make — production.” Copy the secret immediately — it's shown only once.

2

Build the inbound scenario

Start with a trigger module for wherever your clients message you (Gmail, Slack, WhatsApp Business, Zendesk, or a webhook of your own). Add an HTTP → Make a request module, method POST, to the URL below.

Request URL
https://replytime.net/api/v1/events/inbound
3

Configure the request

Set the headers for auth, choose Body type: Raw / JSON, and map the trigger bundle's fields into client, channel, and message.

Headers
Authorization: Bearer rt_xxxxxxxxxxxxxxxxxxxxxxxx
Content-Type: application/json
4

Duplicate it for replies

Clone the scenario, trigger it on your own reply instead, and point the HTTP module at /api/v1/events/outbound. This is the scenario that stops the clock.

5

Run once and check the dashboard

Run the scenario once with real data, then check the client's conversation in the ReplyTime dashboard — the countdown should start and stop as expected.

Example payload

Both endpoints accept the same shape. Set message.source_tool so you can tell where an event came from later.

{
  "client": { "external_ref": "acme-corp", "name": "Acme Corp" },
  "channel": { "type": "email", "identifier": "support@acme.com" },
  "message": {
    "occurred_at": "2026-09-09T10:15:00Z",
    "source_tool": "make"
  },
  "idempotency_key": "gmail-msg-18cf2a91"
}
Full field reference, error codes, and idempotency details:Read the API reference →
Start free trial — 14 days

Make questions, answered

Which Make module should I use?+

HTTP → Make a request. Set the method to POST and the body type to Raw / JSON.

Do I need two separate scenarios?+

Yes — one triggered by an incoming client message (posts to /api/v1/events/inbound), one triggered by your reply (posts to /api/v1/events/outbound). They run independently.

How do I avoid duplicate events on scenario retries?+

Pass idempotency_key set to the source module's own message id. A repeat call with the same key is a safe no-op and won't create a duplicate conversation event.

Can one scenario cover multiple channels?+

Yes — set channel.type per bundle (e.g. from a router), so one scenario can fan out to WhatsApp, email, or Slack events.

Using a different tool?