# Workflow HTTP Request Not Creating Campaign **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** workflows, identity-security-cloud\ **Created:** [June 5, 2024, 1:53pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855 "2024-06-05T13:53:14Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![mosareini](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mosareini/32/6638_2.png) [@mosareini](https://developer.sailpoint.com/discuss/u/mosareini)\ **Post date:** [June 5, 2024, 1:53pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/1 "2024-06-05T13:53:14Z")
Hello, I have a couple workflows I am currently building and they all keep failing any time I use the HTTP Request Action. I downloaded the workflow execution history and this is the error I’m receiving : ![image](https://global.discourse-cdn.com/sailpoint/original/2X/2/21af22d093019a0d96335ad2349420a1520bfd0d.png) I assume the way I set up the HTTP Request authentication is incorrect, and was wondering if anyone else has ran into this issue and solved it? Below is the HTTP Request action and the data I’ve inputted. ![image](https://global.discourse-cdn.com/sailpoint/original/2X/e/ebbc1d2c3ab39a9796820252d760680ae20fca7e.png) ![image](https://global.discourse-cdn.com/sailpoint/original/2X/8/8cae7d586c9a70345c27a74ed62f43a5c0d11ff5.png) For some additional context, I tried running the API from the SailPoint Developer Community page and it works fine. I got a 200 response and the campaign was created in our tenant. I used the Generate Bearer Token API, plugged in the access token and the API worked with no issue. This leads me to believe there’s something wrong with my HTTP Request step that isn’t allowing it to grab the access token. Any help would be much appreciated! ---
**Author:** ![baoussounda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/baoussounda/32/13095_2.png) [@baoussounda](https://developer.sailpoint.com/discuss/u/baoussounda)\ **Post date:** [June 5, 2024, 2:18pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/2 "2024-06-05T14:18:06Z")
Hi @mosareini, Just for remark, why you do note use native **Create Certification Campaign** action ? ![image](https://global.discourse-cdn.com/sailpoint/original/2X/4/411fa40669491818486bee972928130c3875e957.png) It’s simple than http request. Best regards ---
**Author:** ![baoussounda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/baoussounda/32/13095_2.png) [@baoussounda](https://developer.sailpoint.com/discuss/u/baoussounda)\ **Post date:** [June 5, 2024, 2:19pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/3 "2024-06-05T14:19:02Z")
For your error, check client id and client secret authorization. Do you use personal access token (PAT) ? it’s mandatory to use that. As you say : “I used the Generate Bearer Token API” make sure to generate personal access token here : [Managing API Keys and Tokens - SailPoint Identity Services](https://documentation.sailpoint.com/saas/help/common/api_keys.html#generating-a-personal-access-token) ---
**Author:** ![ipobeidi](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ipobeidi/32/16000_2.png) [@ipobeidi](https://developer.sailpoint.com/discuss/u/ipobeidi)\ **Post date:** [June 5, 2024, 2:36pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/4 "2024-06-05T14:36:30Z")
hey @mosareini Be sure that the user has ORG\_ADMIN some apis only allow this access. ---
**Author:** ![mosareini](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mosareini/32/6638_2.png) [@mosareini](https://developer.sailpoint.com/discuss/u/mosareini)\ **Post date:** [June 5, 2024, 3:10pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/5 "2024-06-05T15:10:16Z")
Hi @baoussoundam, This is just a test workflow I built to get the HTTP Request configuration down. When I first started with workflows, the Create Campaign action did not have the ability to set the reviewer as a Governance Group, which made me look into the HTTP Request action. As of recent, SailPoint added an input field to set Governance Groups as reviewers in the Create Certification action, so we are using the Create Campaign action for any workflows that create campaigns. But now, I am at the point where I need to start using the HTTP Request for other workflows I am building, and this test workflow is just something I built to play around with and verify that the HTTP Request is configured properly. ---
**Author:** ![mosareini](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mosareini/32/6638_2.png) [@mosareini](https://developer.sailpoint.com/discuss/u/mosareini)\ **Post date:** [June 5, 2024, 3:15pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/6 "2024-06-05T15:15:34Z")
Hi @ipobeidi, I have Admin user level and for the PAT I selected scopes: all ---
**Author:** ![mosareini](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mosareini/32/6638_2.png) [@mosareini](https://developer.sailpoint.com/discuss/u/mosareini)\ **Post date:** [June 5, 2024, 3:19pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/7 "2024-06-05T15:19:19Z")
Yes, I use the PAT for the ID and Secret. I selected **scopes:all** as well, and I am still running into this issue. ---
**Author:** ![baoussounda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/baoussounda/32/13095_2.png) [@baoussounda](https://developer.sailpoint.com/discuss/u/baoussounda)\ **Post date:** [June 5, 2024, 3:21pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/8 "2024-06-05T15:21:17Z")
It should be work with PAT. Change Credential location to Body or clear it and test again ![image](https://global.discourse-cdn.com/sailpoint/original/2X/a/afe6297897d2bc5a47900382869905f457ec857b.png) ---
**Author:** ![jesvin90](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jesvin90/32/5301_2.png) [@jesvin90](https://developer.sailpoint.com/discuss/u/jesvin90)\ **Post date:** [June 5, 2024, 3:23pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/9 "2024-06-05T15:23:48Z")
Hi @mosareini, There was a recent thread where the issue was resolved after whitelisting the IP’s. You may want to take a look into that as well. > [@Workflow HTTP Operation 401 JWT Required](https://developer.sailpoint.com/discuss/t/workflow-http-operation-401-jwt-required/57323/20): > > Hi All, I’ve tried as well. All works with Postman curl command: curl --location --request POST 'https://\.api.identitynow.com/beta/sources/\/load-accounts' \ --header 'Authorization: Bearer \' \ --header 'Content-Type: application/json' \ --data-raw '{ "disableOptimization": true }' However, my test workflow does not: { "name": "TEST", "description": "", "modified": "2024-05-24T17:04:39.869109823Z", "modifiedBy": { "type": "IDENTITY", "id": "\ **Author:** ![mosareini](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mosareini/32/6638_2.png) [@mosareini](https://developer.sailpoint.com/discuss/u/mosareini)\ **Post date:** [June 5, 2024, 3:56pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/11 "2024-06-05T15:56:30Z") Oh wow, I’ll definitely look into this and report back if it works, thanks Jesvin! ---
**Author:** ![Mike\_Trachta](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mike_trachta/32/4087_2.png) [@Mike\_Trachta](https://developer.sailpoint.com/discuss/u/Mike_Trachta)\ **Post date:** [June 5, 2024, 6:33pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/12 "2024-06-05T18:33:26Z")
Can we please have the relevant documentation updated so that others do not need to figure this out by trial and error? ---
**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Post date:** [June 18, 2024, 7:08pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/13 "2024-06-18T19:08:36Z")
@mosareini did the IP allow list work for you? ---
**Author:** ![mosareini](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mosareini/32/6638_2.png) [@mosareini](https://developer.sailpoint.com/discuss/u/mosareini)\ **Post date:** [June 18, 2024, 8:57pm UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/14 "2024-06-18T20:57:50Z")
@colin_mckibben I gave the IP’s to one of our security engineers, they said there wasn’t any traffic and that they would look into it, but they don’t believe this is the fix as of now. Are there any known issues on your end regarding the authentication problems I’ve been running into? I’m pushing them to just whitelist the IP’s just so I can test and know for a fact that the allow list isn’t the fix. ---
**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Post date:** [June 19, 2024, 1:19am UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/15 "2024-06-19T01:19:10Z")
If this were an issue with your user level, scopes, you would have gotten a 403 instead of a 401. If the IP allow list doesn’t fix this, then this leads me to believe that the configuration is incorrect or this particular workflow is in a bad state and can’t properly retrieve the secrets from the secret manager. Have you tried creating a brand new workflow and configuring a new HTTP request from scratch? ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [August 18, 2024, 1:19am UTC](https://developer.sailpoint.com/discuss/t/workflow-http-request-not-creating-campaign/62855/16 "2024-08-18T01:19:36Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.