Skip to main content

I'm trying to use the HTTPV2 marketplace integration to send an event using the PagerDuty Events enqueue endpoint: API Reference | PagerDuty Developer Documentation

The sensitive parameter in this case is the routing_key, which must be sent as part of the request body. However, when I enter routing_key and the value itself in the integration instance API key field and value, the response is an error stating the routing_key is missing. If I just include the sensitive routing_key in the body, it works just fine but then the routing_key is in plaintext. I know that in the dedicated authentication flow you can use placeholders like integration.token which doesnt fit the authentication method, but is there some way to reference other dedicated placeholders? 

I know I can create a custom integration from scratch, but I was wondering if there was anyway to avoid doing so by utilising the HTTPV2 integration in this case (without exposing the sensitive routing_key in plaintext in the platform)?

cant you just use the Pager Duty integration that is already in the marketplace?  

cant you just use the Pager Duty integration that is already in the marketplace?  


@dnehoda There is a community integration available in Google (so no support by Google) which works with some of the endpoints in the main PagerDuty API (https://api.pagerduty.com API Reference | PagerDuty Developer Documentation). I cannot use this endpoint in my environment (this endpoint also uses a conventional Authorization header), but I can use the more limited V2 Events API (API Reference | PagerDuty Developer Documentation) which sends the routing_key in the body.

TLDR: I cannot use that integration.

Reply


Terms & ConditionsCookie settings
Privacy Policy Terms of Service Gen AI Policy Community Guidelines Cookie Settings

© 2025 Google. All rights reserved.