[Feature Request] API support to pause/close/reopen individual Typebot sessions

[juliomoreirx]

Currently, there's no way to control the status of an individual session via the API — such as pausing, closing, or reopening a bot for a specific user in real time. This creates a limitation when integrating Typebot with live chat platforms (e.g. Chatwoot, Zendesk, etc), where the ideal flow would be:

• The bot handles the initial conversation.

• A human agent takes over, and the bot needs to pause to avoid conflict.

• After the human interaction ends, the bot resumes automatically.

Right now, this can only be handled via frontend hacks or conditional flows inside the bot, which are not reliable and can break easily.

Proposal: PATCH /api/v1/sessions/{sessionId}/status

With a request body such as:

{ "status": "paused" | "closed" | "opened" }

Real-world example: I'm integrating Typebot with Chatwoot. When a human agent joins the conversation, I'd like to send a PATCH request to pause the bot for that session. Once the conversation is marked as resolved in Chatwoot, I would send another PATCH to reopen the bot session. This prevents the bot from sending messages while a human is in control.

Benefits:

• Cleaner integration with CRMs and support platforms.

• Avoids fragile and manual workarounds on the frontend.

• Enables smarter automations and state management based on session status.

Note:

The current workaround using Evolution API 2.0 is not functional for this use case. Implementing native support for session status through the official Meta API integration would be a much more reliable and scalable solution.