When your CustomGPT agent handles conversations, the dialogue itself may be smooth and intuitive — but what happens after the interaction is just as important.
Many teams rely on follow-up steps such as exporting conversations, sending transcripts to support systems, or generating summaries for internal review.
Until now, those steps often required manual effort or unpredictable timing.
With the launch of the Zapier event new Conversation Ended, CustomGPT users now gain a reliable, automated way to detect when a conversation has gone quiet — and use that moment to trigger useful workflows.
This event allows you to automate the follow-up actions that occur after a conversation finishes, without changing anything about how your agent behaves.
It’s designed specifically for Zapier automation, meaning the trigger exists outside the live conversation environment and does not mark or modify the conversation inside CustomGPT.
In this article, we explain what the Conversation Ended trigger is, how it works, and how you can use it to automate more of your workflow with precision, consistency, and minimal effort.
What Is the Conversation Ended Trigger?
The Conversation Ended trigger is a Zapier-specific event that fires after a CustomGPT conversation has gone inactive for 5 minutes. Zapier listens for this inactivity and triggers your automation once that quiet period is detected.
To make sure the event fires at the right moment, this feature uses a simple but effective rule: each time a message is sent in the conversation, the 5-minute timer resets. This ensures the trigger activates only when a conversation genuinely stops, not simply when there is a brief pause.
How it works:
- A conversation is monitored for inactivity.
- If 5 minutes pass after the last message, Zapier receives the Conversation Ended event.
- Any new message restarts the timer from zero.
- The event is sent once per conversation, even if new messages are added afterward.
- When it triggers, Zapier receives a session_id, which is essential for follow-up steps.
What it doesn’t do:
It is very important to note that this event does not affect the actual conversation inside CustomGPT. It:
- Does not end or close the conversation in the dashboard
- Does not change conversation status
- Does not affect the agent or user experience
- Exists only for Zapier automation purposes
This separation ensures that your agent continues functioning normally while Zapier receives exactly the signals it needs to run your workflows at the right moment.
Why This Matters for Automation
Many teams depend on predictable timing for post-conversation work. For example, you may need to export the conversation transcript, send a copy to a support system like Freshdesk, or process the transcript with an AI action to create a summary.
Without an automation trigger tied to the end of a conversation, these tasks can become inconsistent or require manual intervention.
The Conversation Ended event provides a clean and reliable point in time to start these workflows — the moment the conversation goes quiet. Because Zapier receives the event only once per conversation, you avoid duplicate exports, repeated notifications, or multiple workflow triggers for the same chat.
For teams that use CustomGPT agents for support, lead intake, documentation, or any structured communication flow, this event creates a stable foundation for building consistent, automated follow-up steps.
How You Can Use the Conversation Ended Event (Based Only on Provided Details)
Once Zapier receives the Conversation Ended trigger and its session_id, you can connect it to other Zapier actions that rely on that session ID. One common and powerful use case is combining this trigger with the Export Conversation action.
Because Zapier receives the session ID only once per conversation, these actions execute cleanly without duplication.
How to Configure the Conversation Ended Trigger in Zapier Event
Setting up this new trigger is straightforward and accessible to both technical and non-technical users. Below is the step-by-step process based strictly on the information you provided.
Step 1: Log In and Create a Zap
Log in to your Zapier account and click Create Zap to start building your automation. This is where you select what will trigger your automation and what actions will follow.
Step 2: Choose CustomGPT.ai as the Trigger App.
Search for CustomGPT.ai and select it. Zapier will display all available triggers for that app.
Choose the Zapier event named: Conversation Ended
This tells Zapier to watch for conversations that become inactive and trigger your workflow accordingly.
Step 3: Connect Your CustomGPT Account
You’ll be prompted to sign in to your CustomGPT account through Zapier using your API key.
To find or retrieve your API key:
- Log in to CustomGPT
- Go to Deploy > API in your dashboard. Follow the API Key Guide if needed
Paste your key in Zapier when asked. Once authenticated, Zapier can access the necessary information to detect and act on conversation events.
Step 4: Choose the Agent to Monitor
Zapier will show the list of agents you have access to.
Select the agent for which you want to detect the end of conversations. This allows you to set up different workflows for different agents if needed — each Zap can monitor one specific agent.
Step 5: Test the Trigger
Click Test Trigger.
Zapier will pull in recent sample data, including a session_id. This gives you a preview of what Zapier will receive when the actual event occurs, confirming that your setup is working.
Once the test is successful, you are ready to move on to building the action steps.
Building Your Follow-Up Actions Using the Session ID
After the Conversation Ended trigger is configured, Zapier lets you choose what happens next. The session_id returned by the trigger is the key piece of information that ties your follow-up actions to the specific conversation that just ended.
For example, you can:
Export the conversation
Use the session ID to export the entire conversation in the format you need:
- Export Conversation as PDF
- Export Conversation as CSV
These files can be used directly or further processed.
Send the exported conversation to Freshdesk
You can take the PDF or CSV and:
- Attach it to a support ticket
- Send it to the Freshdesk inbox
- Use it as part of a structured workflow
Process the CSV using ChatGPT before sending it
You can add a ChatGPT step in Zapier to:
- Process the CSV
- Extract data
- Prepare summaries
- Clean up content before it’s delivered to Freshdesk
Notify your team
Send confirmations or alerts to team communication channels such as:
- Slack
- Freshdesk notifications
- Microsoft Teams
The system can automatically inform your team that the conversation has ended and has been exported or processed as needed.
These workflows help teams stay organized and respond more effectively — all without impacting the active conversation itself.
Designed for Both Technical and Non-Technical Users
This feature is suitable for everyone:
Non-technical users
- Easy visual setup in Zapier
- No code needed
- Guided steps
- Clear triggers and actions
Technical users
- Reliable trigger timing
- Consistent event logic
- Direct access to session_id
- Ability to build layered workflows involving exports and AI processing
Whether your workflow is simple or advanced, this trigger gives you predictable control over what happens after every conversation.
Conclusion
The Zapier event new Conversation Ended provides a powerful yet simple way to automate what happens once a CustomGPT conversation becomes inactive.
By detecting the moment when a conversation truly ends — and sending the corresponding session ID — this feature gives teams the ability to automate exports, process transcripts, and route information to the right tools and people.
Because the event fires once per conversation and resets with every new message, it gives your automations clear, reliable timing. And because it does not affect the conversation itself, your agent continues operating exactly as before.
Whether you’re using CustomGPT for support, information workflows, or internal operations, the Conversation Ended trigger helps streamline everything that happens after the dialogue finishes — consistently, automatically, and with no manual effort.