feat(pagerduty): add client and client_url support for Events API v2

[jyoti369]

What

Add optional client and client_url parameters to the PagerDuty Events API v2 integration, per the Events API v2 spec.

These fields allow a clickable "View in [client]" link to appear in PagerDuty event details.

Why

The current Events API implementation is missing client and client_url attributes. Without them, events created via Keep don't show the monitoring client link in PagerDuty.

Changes

• Added client and client_url as optional named parameters in _notify, _send_alert, and _build_alert
• Both fields are placed at the top level of the event payload (not inside payload.payload), matching the API spec
• Added unit tests covering:
  • client/client_url included when provided
  • client/client_url omitted when not provided
  • Full payload structure validation

Usage in workflows

actions:
  - name: pagerduty-alert
    provider:
      type: pagerduty
      config: "{{ providers.pagerduty }}"
    with:
      title: "CPU at 99%"
      severity: critical
      client: "Keep"
      client_url: "https://keep.example.com/alerts/123"

Closes #6233

[cursor]

You have used all of your free Bugbot PR reviews.

To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[jyoti369]

Unit test failure is unrelated to this PR - it's a flaky SQLite locking error during teardown in test_workflow_keep_notify_after_foreach:

sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) database table is locked
[SQL: DROP TABLE workflowtoincidentexecution]

938 tests passed, only this one errored due to SQLite concurrency. Could you re-run the failing check?

[jyoti369]

@shahargl The images/links placement has been reverted back to the original nesting inside payload["payload"] as you requested. The PR now only adds the new client and client_url fields at top level (which is correct per the PagerDuty Events API v2 spec). All CI checks are green. Ready for re-review when you get a chance.

[bbcorp]

lgtm
Hey @shahargl can you have a look and confirm it looks good to you too please?

[jyoti369]

@shahargl all review changes are addressed and @bbcorp has lgtm'd. CI is green. Would appreciate a re-review when you get a chance!

[bbcorp]

I've asked Shahar to have a look when he has time.
Shabbat Shalom!

[jyoti369]

Hey @shahargl, all review feedback has been addressed and @bbcorp has approved. CI is green. Ready for final approval when you get a chance. Thanks!

[talboren]

LGTM

[github-actions]

🌈 Fantastic work @jyoti369! Your very first PR to keep has been merged! 🎉🥳

You've just taken your first step into open-source, and we couldn't be happier to have you onboard. 🙌
If you're feeling adventurous, why not dive into another issue and keep contributing? The community would love to see more from you! 🚀

For any support, feel free to reach out on the community: https://slack.keephq.dev. Happy coding! 👩‍💻👨‍💻

[jyoti369]

Hi @talboren, thanks for merging the PagerDuty Event API enhancement! I see Keep offers bounties for contributions - is there a bounty for this PR that I should expect payment for?

[jyoti369]

hey @talboren followin up after a bit. i know keep doesnt run a formal bounty post-acquisition (saw shahars slack note, totally cool). just curious if theres any other way community contributors get recognized for landed work like this - contributor list, swag, anythng? no worries if not, just askin for context