Get Started
Integrate Channel Providers

Demo Integrations

Learn how HubNest default demo Email and SMS providers work, their sending limits, and when to replace them with production integrations.

1

1. Overview of Demo Integrations

Demo integrations are built-in, sandboxed providers for the email and SMS channels. Their purpose is to allow you to test your notification workflows immediately, without needing to sign up for or connect a real third-party provider.

Cloud & Local Sandbox
Demo integrations come pre-configured and active by default in your development workspace so you can test notification delivery in seconds.
2

2. Limits of the demo integrations

To prevent spam abuse and ensure reliable testing for all developers, demo integrations operate under the following rules:

  • Daily Sending Limit: 50 demo emails and 20 demo SMS messages per 24-hour rolling window.
  • Sandbox Domain: Demo emails originate from sandbox@hubnest-test.com.
  • Test Recipient Restrictions: Messages sent via demo SMS can only be delivered to your registered developer phone number.
3

3. How to test using a demo integration

Simply trigger any workflow in your development environment. The gateway will automatically use the active HubNest Demo Provider:

terminal/test-demo-trigger.sh
bash
1curl -X POST "http://localhost:8085/api/v1/events" \
2 -H "Authorization: Bearer hn_live_8f3a91b2c4e567890abcdef123456789" \
3 -H "Content-Type: application/json" \
4 -d '{
5 "eventName": "inbox.welcome",
6 "to": { "subscriberId": "usr_demo_01", "email": "dev@example.com" },
7 "payload": { "title": "Testing Demo Email" }
8 }'
4

4. Replacing Demo with Production Providers

When you are ready to go to production, go to Integration Store in the HubNest dashboard, click Add Provider, enter your production API credentials (e.g. AWS SES IAM keys or Twilio SID), and mark your production provider as Primary.

Was this guide helpful?