Power Platform Community Forum Thread Details

Hello everyone,

I'm trying to build a custom connector in Power Automate to trigger a Jenkins job hosted on our internal Rancher cluster (with LoadBalancer IP).

So far, I’ve configured two actions:
1. **GetCrumb** – using `/crumbIssuer/api/json`, which successfully returns the Jenkins Crumb.
2. **TriggerBuild** – using `/job/statement-sit-CD/buildWithParameters` with POST, Content-Type = `application/x-www-form-urlencoded`.

When I test the connector in Power Automate:
- Crumb is received successfully.
- But the second action returns **Status 500 (Internal Server Error)** from Jenkins.

I’ve already tried:
- Including `Jenkins-Crumb` in headers.
- Adding `token` as query string.
- Changing Content-Type between `application/json` and `application/x-www-form-urlencoded`.
- Using both `/buildWithParameters` and `/build`.

Still getting the same 500 error when executed from Power Automate, while the same call works fine from Postman.

Does anyone have experience triggering Jenkins jobs from Power Automate custom connectors?
Is there a recommended way to handle Jenkins CSRF Crumbs and tokens in Power Automate?

Thanks in advance!

**Environment details:**
- Jenkins 2.516.3 (on Rancher / Kubernetes)
- Power Automate Custom Connector (Security type: Basic Auth)
- Using internal LoadBalancer URL for Jenkins

Categories:

Connector development