# External Trigger with acces request submitted subscription is not working **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** workflows, sailpoint-identity-security\ **Created:** [May 20, 2026, 4:05pm UTC](https://developer.sailpoint.com/discuss/t/external-trigger-with-acces-request-submitted-subscription-is-not-working/209868 "2026-05-20T16:05:15Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![kanusha9](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kanusha9/32/37041_2.png) [@kanusha9](https://developer.sailpoint.com/discuss/u/kanusha9)\ **Post date:** [May 20, 2026, 4:05pm UTC](https://developer.sailpoint.com/discuss/t/external-trigger-with-acces-request-submitted-subscription-is-not-working/209868/1 "2026-05-20T16:05:16Z")
Hi Everyone, For one of my requirement on using access request submitted trigger issue 1. on access request submission the workflow is not getting triggered even if it is enabled. Issue 2. Referring to the Blog > [@Implementing A Request Response Type Trigger in Workflows](https://developer.sailpoint.com/discuss/t/implementing-a-request-response-type-trigger-in-workflows/10216): > > At the time of this writing, SailPoint Workflows does not have native support for our [request response type](https://developer.sailpoint.com/docs/extensibility/event-triggers/trigger-types/#request-response) triggers, such as the [Access Request Submitted trigger](https://developer.sailpoint.com/docs/extensibility/event-triggers/triggers/access-request-submitted). However, there is a way to implement request response triggers using the current capabilities of Workflows. This guide will demonstrate how to configure a Workflow that can successfully receive events from the Access Request Submitted trigger as well as respond wi… I tried to implement the same using external trigger. First generated the new access token from where collected the client id and client secret which I used to generate the access token and used for access request submitted subscription but on test subscription getting error either 401 unauthorized or Invocation timed out in the activity log ![image](https://global.discourse-cdn.com/sailpoint/original/3X/b/d/bde57859ae787452c63ffb0fcd0cfb57f00f34d1.png) Can someone help me understand where I am doing wrong and why is this behaviour? TIA ---
**Author:** ![ashishbhatia](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ashishbhatia/32/25152_2.png) [@ashishbhatia](https://developer.sailpoint.com/discuss/u/ashishbhatia)\ **Post date:** [May 20, 2026, 5:42pm UTC](https://developer.sailpoint.com/discuss/t/external-trigger-with-acces-request-submitted-subscription-is-not-working/209868/2 "2026-05-20T17:42:54Z")
Have you generated the bearer token? Via API client or curl command? ---
**Author:** ![kanusha9](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kanusha9/32/37041_2.png) [@kanusha9](https://developer.sailpoint.com/discuss/u/kanusha9)\ **Post date:** [May 21, 2026, 5:09am UTC](https://developer.sailpoint.com/discuss/t/external-trigger-with-acces-request-submitted-subscription-is-not-working/209868/3 "2026-05-21T05:09:51Z")
- In External Trigger → generated client credentials by clicking new access token - Then used in cURL → to generate bearer token - Then used that token in Trigger Subscription ---
**Author:** ![KRM7](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/krm7/32/2685_2.png) [@KRM7](https://developer.sailpoint.com/discuss/u/KRM7)\ **Post date:** [May 21, 2026, 7:12am UTC](https://developer.sailpoint.com/discuss/t/external-trigger-with-acces-request-submitted-subscription-is-not-working/209868/5 "2026-05-21T07:12:20Z")
dude, don’t display your secrets and tokens, please delete this message ---
**Author:** ![sagar\_kamalakar](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sagar_kamalakar/32/18893_2.png) [@sagar\_kamalakar](https://developer.sailpoint.com/discuss/u/sagar_kamalakar)\ **Post date:** [May 21, 2026, 2:11pm UTC](https://developer.sailpoint.com/discuss/t/external-trigger-with-acces-request-submitted-subscription-is-not-working/209868/6 "2026-05-21T14:11:41Z")
I recently faced a similar issue. You can generate a new access token, which will overwrite the existing one. Be sure to copy the client ID and secret and store them securely. Then, use Postman or any REST client to generate the token and paste it into the subscription. Also, confirm that your integration URL is correct, for example: [https://tenant.api.identitynow/beta/workflows/execute/external/[workflowId]](https://tenant.api.identitynow/beta/workflows/execute/external/%5BworkflowId%5D) and ensure the subscription type is set to HTTP. ---
**Author:** ![kanusha9](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kanusha9/32/37041_2.png) [@kanusha9](https://developer.sailpoint.com/discuss/u/kanusha9)\ **Post date:** [May 26, 2026, 6:24am UTC](https://developer.sailpoint.com/discuss/t/external-trigger-with-acces-request-submitted-subscription-is-not-working/209868/7 "2026-05-26T06:24:48Z")
I tried generating multiple tokens using the external link until it gives success then configuring it in the subscription has actually worked fine Thank you all for the response. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [July 25, 2026, 6:25am UTC](https://developer.sailpoint.com/discuss/t/external-trigger-with-acces-request-submitted-subscription-is-not-working/209868/8 "2026-07-25T06:25:34Z")
Closed on July 25, 2026, 6:25am UTC This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.