Why is the Outlook new email trigger not firing in my Pipedream connect prod version when a new email arrives in my inbox?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

/@U05A7KLNALC I am using PIpedream connect prod version. I have configured a outlook new email trigger with my webhook for my email. But, the trigger is not firing when a new email hits my inbox. Please let me know what is wrong or how can I fix it? Here is the trigger data found by calling the GET deployed trigger api:

{
   "data":{
      "id":"dc_dAuJ8LN",
      "created_at":1771502601,
      "updated_at":1771502601,
      "active":true,
      "component_id":"sc_B5iB4ELn",
      "component_key":"microsoft_outlook-new-email",
      "configurable_props":[
         {
            "name":"microsoftOutlook",
            "type":"app",
            "app":"microsoft_outlook"
         },
         {
            "name":"http",
            "type":"$.interface.http",
            "customResponse":true
         },
         {
            "name":"db",
            "type":"$.service.db"
         },
         {
            "name":"timer",
            "type":"$.interface.timer",
            "label":"Webhook renewal timer",
            "description":"Graph API expires Outlook notifications in 3 days, we auto-renew them in 2 days, [see](https://docs.microsoft.com/en-us/graph/api/resources/subscription?view=graph-rest-1.0#maximum-length-of-subscription-per-resource-type)",
            "default":{
               "intervalSeconds":172800
            }
         },
         {
            "name":"folderIds",
            "type":"string[]",
            "label":"Folder IDs to Monitor",
            "description":"Specify the folder IDs or names in Outlook that you want to monitor for new emails. Leave empty to monitor all folders (excluding \"Sent Items\" and \"Drafts\").",
            "remoteOptions":true,
            "optional":true
         }
      ],
      "configured_props":{
         "microsoftOutlook":{
            "authProvisionId":"apn_P8hz54Q"
         },
         "http":{
            "endpoint_url":"https://d80dda7ae9dd2165e2f66c603b9d4517.m.pipedream.net"
         },
         "db":{
            "type":"$.service.db"
         },
         "timer":{
            "cron":null,
            "interval_seconds":172800
         }
      },
      "name_slug":"langoedge-dev-project---exu-x1i3de-d",
      "name":"langoedge-dev-project - exu_x1i3deD",
      "owner_id":"exu_x1i3deD",
      "type":"DeployedComponent",
      "emit_on_deploy":true
   }
}

And here is the webhook data found by calling List trigger webhooks:

{"webhook_urls":["https://dev.langoedge.com/api/pipedream/triggers/webhook/69950187f669b8ea93f706f1"]}

cc: @U02A06JPKEH

2

Please note here is the log from sources:

image.png
image.png2333×1041 140 KB

3

/@U05A7KLNALC /@U02A06JPKEH a gentle reminder

4

Thank you for your patience. Let’s troubleshoot why your Pipedream Connect “Outlook New Email” trigger is not firing. ### Key Points from Your Setup - Trigger: microsoft_outlook-new-email - Active: true - Webhook endpoint: Set to your URL (looks correct) - Configured with Outlook auth - No folderIds specified: Should monitor all folders except Sent/Drafts by default — ## Common Reasons the Outlook “New Email” Trigger Doesn’t Fire ### 1. Microsoft Graph Subscription Expiry - Outlook’s webhook subscriptions expire every 3 days and must be renewed. Your config shows the timer is set to auto-renew every 2 days, which is correct. - If the renewal fails (e.g., due to revoked permissions or expired tokens), the subscription lapses and triggers stop firing. ### 2. Authentication Issues - If the Outlook OAuth token expires or is revoked, Pipedream can’t renew the webhook or receive events. - Try reconnecting your Microsoft Outlook account in Pipedream to refresh the token. ### 3. Permissions/Scopes - The connected Outlook account must have the right permissions (usually Mail.Read or Mail.ReadWrite). - If you changed permissions in Azure after connecting, you may need to reconnect the app. ### 4. Folder Monitoring - By default, all folders except Sent/Drafts are monitored. If you want to monitor a specific folder, set folderIds. - If your emails are routed to a custom folder by rules, and that folder isn’t monitored, the trigger won’t fire. ### 5. Webhook Endpoint Issues - Your webhook endpoint should be reachable from the public internet. If it’s down or returns errors, events may not be delivered. - Test your endpoint with a tool like Webhook.site or by sending a manual POST. ### 6. Pipedream Source Logs - Check the Source Logs in Pipedream for errors related to webhook renewal, delivery, or authentication. — ## What To Do Next 1. Reconnect your Microsoft Outlook account in Pipedream to refresh tokens and permissions. 2. Check Source Logs for errors (especially about subscription renewal or delivery). 3. Send a test email to your inbox (not Sent/Drafts) and see if the trigger fires. 4. Check if emails are routed to a folder by rules—if so, specify that folder in folderIds. 5. Test your webhook endpoint to ensure it’s reachable and returns a 2xx status. — ## If the Issue Persists If you’ve checked all the above and it’s still not working, please: - Share any error messages from the Source Logs. - Confirm if the Outlook account is a personal or business account (sometimes business accounts have extra restrictions). - Visit Pipedream for direct support from the Pipedream team. — Let me know what you find in the logs or if you need more help!