Strava trigger gives 'Bad Request'

Questions
1

Hey there,

as i wasn’t asked for it in the credentials - is it not using the refresh tokens as documented here? https://developers.strava.com/docs/authentication/

having had this implemented in php yet i know that it’s definitly needed, otherwise it doesn’t work for long. in any case my webhook urls do look fine and work with other apis as well - and i think the strava trigger did work right after i had added credentials couple of weeks ago.

Describe the problem/error/question

can’t activate any flow with a Strava Trigger in it.

What is the error message (if any)?

image
image388×235 9.72 KB

Information on your n8n setup

core

  • n8nVersion: 1.114.3
  • platform: docker (self-hosted)
  • nodeJsVersion: 22.19.0
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: b4ccc0ca-627e-4f79-8ad7-ead7d05f5e8b

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/140.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2025-10-06T18:02:01.198Z

2

I have exactly the same issue - I’ve tried so many different trouble shooting avenues but just can’t get the either the trigger to Execute by itself or the workflow to Activate.

It seems like the n8n webhook URL doesn’t stay live long enough.

I can use the Get Many Strava node so I know my credentials work.

core

  • n8nVersion: 1.114.3
  • platform: docker (self-hosted)
  • nodeJsVersion: 22.19.0
  • nodeEnv: production
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: ***

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/140.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2025-10-14T01:31:38.904Z

also

  1. Behind Cloudflare Tunnel (not a reverse proxy)
  2. Webhook bypass is configured correctly (tested with curl)
3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.