Lindy Community Icon

Troubleshooting Handle In Same Task Setting for Webhook Trigger

·
·

Good morning! Has anyone here been able to get the “Handle In Same Task” setting of the Webhook Received trigger to work? I’m trying to have multiple posts to the web hook from the same user be processed inside the same task.

  • Avatar of Jonas N.
    Jonas N.
    ·
    ·

    I'm having the same issues actually! I don't want to have to create a new task for each new interaction with the same user. I'd rather keep it all in the same task. Any help and advice would be highly appreciated

  • Avatar of Marvin A.
    Marvin A.
    ·
    ·

    Hi there! Heads up—this will be a bit more technical. But since you’re already using these advanced features, I’m guessing you’ll be just fine! 😄 I’ve tested the “Handle in Same Task” feature with webhooks, and here’s how to make it work: When you set the webhook to “Handle in Same Task” (as shown in the workflow screenshot), Lindy will process multiple webhook requests from the same user in the same conversation/task, rather than creating a new task each time. How to Set It Up 1. Configure your webhook trigger with “Handle in Same Task” selected in the follow-up behavior dropdown. 2. Send your initial webhook request to Lindy. 3. For follow-up requests, you have two options: Option 1: Use the followUpUrl that Lindy provides in its response

    // Example response from Lindy:
    {
      "data": {
        "conversationId": "YYYYYYYYYY",
        "conversationUrl": "https://chat.lindy.ai/email-triager-XXXXXXXX/tasks?conversationId=YYYYYYYYYY",
        "followUpUrl": "https://public.lindy.ai/api/v1/webhooks/lindy/XXXXXXXX?conversationId=YYYYYYYYYY"
      }
    }

    Simply send your follow-up request to this followUpUrl (requires the follow-up action to be set up in your Lindy workflow). Option 2: Include the conversationID in your next webhook request as query parameter Example: Call https://public.lindy.ai/api/v1/webhooks/lindy/YOUR_WEBHOOK_ID?conversationId=YYYYYYYYYY (don’t forget the Secret key inside your call!) Make sure your webhook is configured with “Handle in Same Task” and include the conversationID from the initial response in your subsequent requests. The key is to store either the followUpUrl or conversationID from the initial response and use it for all subsequent interactions with the same user. For more detailed information, check out the Lindy Webhook Trigger Guide: https://www.lindy.ai/academy-lessons/webhook-triggers Hope this helps! Let me know if you have any questions.

  • Avatar of Marvin A.
    Marvin A.
    ·
    ·

    Super quick and dirty example for the Post request to Callback might look like in a flow (but you can also go for option 2 which might be more straight forward)

  • Avatar of Aaron E.
    Aaron E.
    ·
    ·

    Wow, thank you for the detailed explanation Marvin A. — Will work to implement this in the next few days! You should add this to the guide you posted (which I read fully before posting this question) 🙂

  • Avatar of Marvin A.
    Marvin A.
    ·
    ·

    Thanks for the feedback! Aaron E. Totally will add this! But lmk if you encounter any unforeseen issues along the way 🙂

  • Avatar of Julia B.
    Julia B.
    ·
    ·

    Hi Marvin A.! I'm trying to set up Option 2, storing the conversationUrl in my database and then sending it along the next requests - unfortunately a new task is still being created every time Just to make sure where should the conversationUrl be sent? in the headers or in the POST body like

    {
      "conversationUrl": "<user_conversation_url>",
    }

    Any help would be appreciated 🙂

  • Avatar of Marvin A.
    Marvin A.
    ·
    ·

    SORRY! Tiny mistake on my end here. Instead of returning the conversationURL → use the conversationID as a query parameter Example: https://public.lindy.ai/api/v1/webhooks/lindy/YOUR_WEBHOOK_ID?conversationId=YYYYYYYYYY I just double-checked on my end: works! Hope this will clear things up!

  • Avatar of Julia B.
    Julia B.
    ·
    ·

    Perfect that worked out! Thanks for the fast reply