Follow-up closure webhook

Receive a notification when a text agent’s follow-up process finishes its stages or the AI decides further follow-up is unnecessary. Configure Text agent → Advanced → Follow-ups → Close webhook. Text-agent follow-ups are Experimental. This webhook does not represent every manual inbox closure. For a rule triggered by conversation closure, use inbox automations.

Payload

The body has top-level event fields, with no data envelope.

Example

{
  "event": "follow_up_closed",
  "threadId": "55555555-5555-4555-8555-555555555555",
  "agentId": "11111111-1111-4111-8111-111111111111",
  "closureReason": "all_stages_completed_no_response",
  "closureReasonDescription": "Todas las etapas de seguimiento fueron completadas sin recibir respuesta del usuario",
  "totalStages": 3,
  "currentStage": 3,
  "closedAt": "2026-10-15T16:00:00.000Z",
  "contact": {
    "id": "33333333-3333-4333-8333-333333333333",
    "phone": "+15555550102",
    "name": "Demo contact"
  },
  "conversationSummary": "The customer has not replied to the follow-up messages."
}

string

follow_up_closed.

string

Conversation ID. Use it to correlate the follow-up with your conversation record.

string

Text-agent ID.

string

all_stages_completed_no_response or ai_determined_conversation_resolved. Branch on this stable value, not the description.

string

Human-readable reason. The current descriptions are Spanish.

number

Configured stage count.

number

Current stage, numbered from 1.

string

ISO timestamp of the closure notification.

object | null

Contact information when available.

Mostrar Contact fields

string | null

Contact ID.

string | null

Contact phone number.

string | null

Contact name.

string

Summary supplied by the follow-up process.

string

Additional AI reasoning when provided. Can be omitted.

Process the event

No response
Resolved by AI

Use all_stages_completed_no_response to record that the sequence finished without a reply. A human task or CRM update can be appropriate; do not automatically start another unlimited sequence.

Use ai_determined_conversation_resolved to record the decision and inspect conversationSummary and optional aiAnalysisReason. This is the AI’s interpretation, not independent proof that an external business action completed.

Delivery behavior

The configured method is POST or PUT. The sender uses JSON and a 10-second timeout. It does not provide the same automatic retry flow as call webhooks; a delivery failure does not block the conversation’s follow-up process. Record accepted events and your action results in the receiver. For duplicate handling, correlate by conversation, agent, and closure notification; a conversation can have more than one follow-up cycle. Do not treat the conversation ID alone as a permanent one-time key.

Configure text follow-ups

Stages, cumulative timing, schedules, and closure.

Build a follow-up workflow

Choose conditions, map data, and verify the action.

Documentación API

Voz

WhatsApp (WABA)

Canales y conversaciones

Organización

Agentes

Contactos

Etiquetas

Llamadas

Tareas

Números de teléfono

Payload

Process the event

Delivery behavior

Configure text follow-ups

Build a follow-up workflow

​Payload

​Process the event

​Delivery behavior

Configure text follow-ups

Build a follow-up workflow

Payload

Process the event

Delivery behavior