Demo Integrations
Learn how HubNest default demo Email and SMS providers work, their sending limits, and when to replace them with production integrations.
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.
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. 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:
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.
Next steps
Configure AWS SES IAM keys, verified domains, and sending rate limits.
Connect SendGrid API Keys and verified sender identities.
Connect Twilio Account SID, Auth Token, and phone numbers.
Connect Meta WhatsApp Cloud API access tokens and phone number IDs.