Alon J.

Hey Daniela! Hmm, it does look removed. Let me send a note to my team

Hey Daniela! These prices should be available across the board now. Is that what you mean?

Hey Lauren! Thanks for flagging, I'll escalate this to our eng team. Reagrding on error handling, unfortunately not at the moment 😞 I'll re-escalate though, but not sure I have an ETA as this is a unique case in our legacy product!

Hey Deuce - I'll send u a DM shortly!

Hey Patrick! Oh no, not an ideal experience for sure. Do you mind sending over an example where you've attempted to use Outlook, but it used Google instead? I'll take a look and see to override this. On a side note, are you looking to use Google at all? A surefire way to correct this would be to fully remove your Google connections in your Connections page!

Hey Jeff! Great question. Although not something we've fully fleshed out, I've just prompted my assistant below, which then provided me a webhook and added a trigger on the backend. I haven't fully tested this out but it seems doable! 🙂

I use Krisp for meetings. Anytime my meeting ends, I want to send a webhook to Lindy Assistant. Can you setup a webhook trigger and provide me the webhook so I can provide it to Krisp?

Awesome :)

Hey Lauren! This generally happens when you use a variable in the action is using an outdated variable. For example, if you deleted an action/trigger upstream and replaced it while leaving the variable for the old trigger/action, it will cause this issue. Is this a consistent issue? What I would do is delete these variable and reset them. Please let me know if that resolves it. If not, would be happy to flag to our eng team 🙏

Hey Patrick! Are you able to try these instructions? 1. Click on Home within your workspace 2. Once you’re at your home, the URL in your browser should look something like this the image 3. From here, please replace /home with /migrate-to-outlook You will be redirected to a webpage that will prompt you to connect to Outlook! Let me know if that helps

Hey Lauren! I believe it’s because having multiple “message received” triggers in a single workflow would make the execution logic ambiguous. The system wouldn’t know which path to follow or when to re-enter the workflow, which can lead to conflicts.