posthog icon indicating copy to clipboard operation
posthog copied to clipboard

feat(cdp): Add Kudosity SMS destination template

Open t--becker opened this issue 2 months ago • 9 comments

Summary

Adds a new destination template for Kudosity SMS integration, enabling users to send SMS alerts when PostHog events or metrics cross thresholds.

Changes

  • New Kudosity SMS destination template with optimized labels and descriptions
  • Official Kudosity brand icon added
  • Template registered in cdp/templates/init.py
  • Fixed missing /api/hog_functions/templates/ endpoint

Use Cases

  • Operational monitoring (alert on-call teams when metrics breach)
  • Business metrics tracking (SMS when KPIs cross thresholds)
  • On-call notifications and incident response

Testing

  • ✅ Template successfully sends SMS via Kudosity API v2
  • ✅ Variable substitution working (event and person properties)
  • ✅ Authentication with x-api-key header verified
  • ✅ Integration tested end-to-end in local dev environment
  • ✅ Debug mode logging verified

Template Features

  • E.164 phone number format with clear validation
  • Template variable support for dynamic content
  • Message length guidance (160 char standard, auto-split)
  • Link tracking for engagement analytics
  • Developer trial signup link for easy onboarding

API Documentation

Based on Kudosity API docs: https://developers.kudosity.com/reference/post_v2-sms

t--becker avatar Oct 20 '25 04:10 t--becker

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week. If you want to permanentely keep it open, use the waiting label.

posthog-bot avatar Oct 28 '25 07:10 posthog-bot

This PR is ready for review. The Kudosity SMS destination template is complete and tested. All feedback from the initial review has been addressed.

t--becker avatar Oct 29 '25 01:10 t--becker

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week. If you want to permanentely keep it open, use the waiting label.

posthog-bot avatar Nov 11 '25 07:11 posthog-bot

👋 Following up after 3+ weeks. This PR is complete with:

✅ Template implementation ✅ Unit tests added (Nov 4) ✅ All feedback addressed ✅ Manual integration testing verified

@PostHog/team-replay-and-cdp - Could someone please take a look when you have a moment? Happy to make any changes needed. Thanks! 🙏

t--becker avatar Nov 13 '25 00:11 t--becker

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week. If you want to permanentely keep it open, use the waiting label.

posthog-bot avatar Nov 21 '25 07:11 posthog-bot

This PR was closed due to lack of activity. Feel free to reopen if it's still relevant.

posthog-bot avatar Nov 28 '25 07:11 posthog-bot

Thanks @havenbarnes for the fixes and approval! ��

Is there anything else needed to get this merged, or are we just waiting for CI to pass?

t--becker avatar Dec 09 '25 00:12 t--becker

Thanks @havenbarnes for the fixes and approval! ��

Is there anything else needed to get this merged, or are we just waiting for CI to pass?

t--becker avatar Dec 09 '25 00:12 t--becker

Thanks @havenbarnes for the fixes and approval! ��

Is there anything else needed to get this merged, or are we just waiting for CI to pass?

Of course! Sorry again for the delay on this.

Nothing needed on your end, I'll make sure the CI passes and this gets merged tomorrow

havenbarnes avatar Dec 09 '25 05:12 havenbarnes