Integrate Channel Providers
Integrate Channel Providers
Connect email, SMS, WhatsApp, and mobile push notification providers to your HubNest organization.
1
1. Channel Integration Lifecycle
Integrating any delivery channel in HubNest follows a simple 3-step visual and programmatic pipeline:
- Step 1: Obtain Credentials - Retrieve API keys, tokens, or IAM credentials from your provider (e.g. AWS SES, Twilio, Meta Developer Console).
- Step 2: Save in Developer Dashboard - Go to your HubNest Developer Portal > Integrations > Store, select the provider, enter your credentials, and click save. The system encrypts them using Jasypt AES-256.
- Step 3: Dispatch Programmatically - Send notifications by executing a trigger request (POST /api/v1/events) from your application backend.
2
2. Supported Channels & Adapters
HubNest unifies messaging providers across 4 primary transactional channels:
- Email: AWS SES, SendGrid.
- SMS: Twilio, MSG91.
- WhatsApp: Meta WhatsApp Business Cloud API.
- Push: Google Firebase Cloud Messaging (FCM), Apple Push Notification service (APNs).
3
3. Provider Health Scoring & Failover
HubNest dynamically tracks provider delivery success rates and latency. If AWS SES drops or rate limits, traffic automatically redirects to SendGrid.
Next steps
AWS SES Email
Configure AWS SES IAM keys, verified domains, and sending rate limits.
SendGrid Email
Connect SendGrid API Keys and verified sender identities.
Twilio SMS Provider
Connect Twilio Account SID, Auth Token, and phone numbers.
WhatsApp Business
Connect Meta WhatsApp Cloud API access tokens and phone number IDs.
Was this guide helpful?