Advanced Webhook Triggers
The DataFlows SMS Connector provides 16+ business automation triggers to streamline your operations and enhance customer communications.
SMS Communication Triggers
1. SMS Received
Use Case: Automate responses to incoming customer messages
- Trigger: When SMS is received on specific virtual number
- Data Available: Sender phone, message content, timestamp, virtual number
- Common Actions: Auto-reply, create support ticket, update CRM
2. SMS Status Changed
Use Case: Track delivery status and handle failed messages
- Trigger: When SMS delivery status updates (delivered, failed, pending)
- Data Available: Message ID, status, recipient, timestamp
- Common Actions: Retry failed messages, update delivery logs, notify sales team
Business Operations Triggers
3. Balance Low
Use Case: Prevent service interruption with automated alerts
- Trigger: When SMS credits fall below threshold
- Data Available: Current balance, threshold amount, account details
- Common Actions: Send admin alert, auto-purchase credits, notify finance team
4. Campaign Completed
Use Case: Track marketing campaign performance
- Trigger: When bulk SMS campaign finishes sending
- Data Available: Campaign ID, total sent, delivery rates, completion time
- Common Actions: Generate report, notify marketing team, trigger follow-up campaigns
5. Campaign Failed
Use Case: Handle campaign issues immediately
- Trigger: When campaign encounters errors or fails
- Data Available: Campaign ID, error details, affected recipients
- Common Actions: Alert administrators, retry campaign, investigate issues
6. Campaign Started
Use Case: Monitor campaign launch and execution
- Trigger: When new campaign begins sending
- Data Available: Campaign details, scheduled time, recipient count
- Common Actions: Log campaign start, notify stakeholders, monitor progress
Contact Management Triggers
7. Contact Added
Use Case: Welcome new subscribers and update systems
- Trigger: When new contact is added to groups
- Data Available: Contact details, group assignment, custom fields
- Common Actions: Send welcome message, update CRM, add to nurture sequence
8. Contact Updated
Use Case: Sync contact changes across systems
- Trigger: When contact information is modified
- Data Available: Contact ID, changed fields, previous values, new values
- Common Actions: Update external databases, send confirmation, log changes
9. Contact Deleted
Use Case: Handle opt-outs and data removal
- Trigger: When contact is removed from system
- Data Available: Contact details, deletion reason, timestamp
- Common Actions: Update suppression lists, notify compliance team, clean external systems
Messaging Automation Triggers
10. Message Scheduled
Use Case: Confirm scheduled message setup
- Trigger: When message is scheduled for future delivery
- Data Available: Schedule details, recipient info, message content
- Common Actions: Send confirmation, log schedule, update calendar
11. Message Cancelled
Use Case: Handle cancelled scheduled messages
- Trigger: When scheduled message is cancelled
- Data Available: Message ID, cancellation reason, original schedule
- Common Actions: Notify administrators, update logs, handle refunds
12. Keyword Matched
Use Case: Automate responses to specific keywords
- Trigger: When incoming SMS contains predefined keywords
- Data Available: Keyword matched, sender details, message content, match type
- Common Actions: Send specific response, route to department, update customer status
13. Auto Reply Sent
Use Case: Track automated response performance
- Trigger: When automatic reply is sent to customer
- Data Available: Original message, reply content, sender details
- Common Actions: Log interaction, update customer record, measure response rates
Performance Monitoring Triggers
14. Delivery Rate Low
Use Case: Maintain high delivery quality
- Trigger: When message delivery rate drops below threshold
- Data Available: Current rate, threshold, affected campaigns
- Common Actions: Alert administrators, investigate carrier issues, adjust sending patterns
15. High Bounce Rate
Use Case: Protect sender reputation
- Trigger: When message bounce rate exceeds limits
- Data Available: Bounce rate, affected numbers, bounce reasons
- Common Actions: Clean contact lists, investigate number quality, pause campaigns
Administrative Triggers
16. Sender ID Approved
Use Case: Activate new branded messaging
- Trigger: When custom sender ID receives approval
- Data Available: Sender ID details, approval date, restrictions
- Common Actions: Notify marketing team, update available options, launch branded campaigns
17. Sender ID Rejected
Use Case: Handle sender ID application issues
- Trigger: When sender ID application is rejected
- Data Available: Sender ID, rejection reason, resubmission guidelines
- Common Actions: Alert administrators, review requirements, prepare resubmission