Power Platform Community Forum Thread Details

Hello Team,

I’m working on automating the process of sending participant details from bookings on my shared MS Bookings calendar to HubSpot. I have set up a flow using the trigger “When an event is added, updated or deleted (V3)” with the correct calendar ID.

In the flow, I use a Compose action to extract data such as subject, date & time, and the participant’s email address. Then, I use the email address in an HTTP request with my API key to search for the contact in HubSpot. When a match is found, I parse the JSON response and update the relevant CRM properties in HubSpot.
However, when I run the flow, I receive the error: Bad Gateway.

I’ve attached screenshots for reference. I would greatly appreciate any assistance or suggestions.
Thank you in advance.

Categories:

Using flows

Hi @AC-20051300-0

Firstly thank you for the pictures. Just as an FYI, unfortunately the pictures are nice from a flow step direction but do not show the inner configurations of what you did, so its possible that your trigger is actually misconfigured.

So showing your actions (opened) and each configured, then secondarily and more importantly the flow Run that failed, with it opened.

Now, as to your issue.

I'd like you to try these things

1. Delete your Trigger and readd it and reconfigure it. Save it. Publish all customizations.

If #1 doesn't solve it

2. Make sure that the user connection has Read/Write/Admin access to the Shared Calendar, sometimes we have 1 but not the others

If that doesn't help

3. Can you go into Outlook (the app). Try to add the shared Calendar to YOUR outlook instance. I don't know if you have individual permissions to the calendar or if it's a security glitch because if you cannot add it, it WILL give you that error.

If you can open it try to add something to it and if it fails, then we need to look at the configuration of the mailbox/calendar

If that doesn't help

4. Create another Flow, just add that trigger and a simple compose

See if that works.

If none of those work, I would suggest (if its not too late) to create another calendar and try to use it. See if the problem goes away.