How can I make a LeadConnector Conversational AI bot repeatedly request package tracking status from a Zapier webhook in the same conversation?
I'm building a package tracking chatbot using LeadConnector (HighLevel) Conversational AI and Zapier, and I'm stuck on making the flow repeat without ending the conversation. Current Flow The AI router detects when the user wants to track a package. Then the…
I'm building a package tracking chatbot using LeadConnector (HighLevel) Conversational AI and Zapier, and I'm stuck on making the flow repeat without ending the conversation. Current Flow The AI router detects when the user wants to track a package. Then the flow is: AI Message → Ask for tracking number. Capture Information → Save tracking number. Webhook → Send tracking number to Zapier. Zapier: Catch Hook Find Package (API) Request Tracking Status (API) Run JavaScript (format response) Update LeadConnector Contact Update Opportunity Back in LeadConnector → Display the tracking status. Everything works correctly. The problem is that once the flow finishes, it ends. If the user later says: or the bot doesn't go back through the same process. The conversation flow has already finished. What I want I want the conversation to behave like this: User: Track my package. Bot: Sure! What's your tracking number? User: 9400XXXX Bot: Delivered July 8 at 2:34 PM User: Thanks. User: Can you track another package? Bot: Of course! What's the tracking number? User: 1ZXXXX Bot: In Transit Expected tomorrow User: Track another one. Bot: Sure! What's the tracking number? Essentially I want the tracking flow to be reusable indefinitely during the same conversation. My question Is there a way in LeadConnector Conversational AI to: Loop back to the "Ask for tracking number" step? Re-trigger the same webhook multiple times within one conversation? Restart only that branch without ending the conversation? Or is the intended approach to use a Custom Trigger instead of a normal conversation flow? I've attached screenshots of both the LeadConnector conversation flow and the Zapier workflow. Has anyone implemented a reusable "tool" or looping workflow like this? Any guidance would be greatly appreciated.
已收录讨论
the issue is ur building this as a linear flow when it needs to be intent based, leadconnector flows arent really built for true looping back to a step, they run once and end better approach: instead of a flow, set this up as a custom trigger/tool the AI can call whenever it detects tracking intent, not tied to one linear sequence. so every time the ai router detects user wants to track a package (whether its message 1 or message 10 in the convo), it calls the same webhook tool fresh, asks for tracking number, gets response, displays it, then just... waits for the next intent naturally instead of the flow "ending" this is basically the difference between a decision tree (what u built) and a tool the AI has access to and can call repeatedly (what u actually need). leadconnector's AI employee/agent setup with custom actions handles this better than the flow builder for repeatable actions like this if ur stuck on the flow builder specifically, check if they support always listening for this trigger phrase rather than a linear sequence, some platforms let u define reusable sub flows the main convo can jump into anytime vs a single beginning to end path how is ur AI router currently set up to detect the tracking intent, keyword based or is it using their AI classification
The Zap should trigger whenever LeadConnector sends it a webhook, so it might be worth checking the "Allow re-entry" and "Stop on response" settings in LeadConnector (under workflow settings). It seems those control whether a contact can re-enter the same workflow and trigger it again in the same conversation. Let us know how it goes!
I would treat package tracking as a reusable, mostly stateless tool call rather than a loop. When tracking intent appears, store a small pending state for that conversation. If no tracking number is present, ask for it; once it arrives, call the same Zap with conversation ID, request ID, and tracking number, return the result, then clear the pending state. Do not rely on one permanent contact field for the number or result, because a second request can overwrite the first. Use request ID plus tracking number as an idempotency key so a webhook retry cannot create duplicate updates. The LeadConnector re-entry setting may make the current flow run again, but an intent-triggered tool with explicit state will be easier to reuse and debug.