Introduction
Overview Getting started
Channels
Overview SendGrid Mailgun Amazon SES Postmark Mailjet Firebase Push Twilio SMS Plivo SMS Slack Webhooks Twitter
Templates
Overview Templating engine Macros
Contacts
Overview Segments
Messages
Overview Send a message
API
Overview Libraries Contacts Messages
Pricing Docs Contact About Login Signup

Messages

Now that your channels are connected, your notifications and templates ready and you know how to store some data in your contacts, let's see how Notifuse handles your messages!

Message lifecycle

Here is what happens when Notifuse receives a new message:

  1. The payload is verified. If the format is not correct, the message is refused.
  2. The contact attached to the message is upserted.
  3. The message is saved in the database.
  4. If the message is not scheduled to be sent later, it's queued for sending.
  5. A worker pulls the message and send it to your channel.
  6. If your channels webhooks are configured, the status of your message is updated in Notifuse (delivered, opened, clicked...).
Status Side
scheduled Notifuse The message is scheduled to be sent in the future...
queued Notifuse The message is on the launch pad!
sent Notifuse The message has been accepted by the channel, from now if something wrong happens it's gonna be the responsability of the channel.
failed Notifuse Something wrong happened on the Notifuse side! Most of the time it's because the channel refused the message (wrong API keys...).
delivered Channel Status updated via webhooks. The channel confirmed the delivery of the message.
dropped Channel Status updated via webhooks. For any reason the message has been dropped (rejected, hard bounce...).
bounce Channel Status updated via webhooks. Used by Email Service Providers, the message soft-bounced and should be delivered anytime soon by the channel.
spam Channel Status updated via webhooks. Bad news, the message has been marked as "spam" by the recipient, you should remove this contact from your list.
opened Channel Status updated via webhooks. The message has been opened by the recipient. Requires a channel that handles "open tracking".
clicked Channel Status updated via webhooks. The message has been clicked by the recipient. Requires a channel that handles "click tracking".
unsubscribed Channel Status updated via webhooks. The recipient clicked on the "unsubscribe link". Requires a channel that handles "unsubscribe tracking".

Next: Sending some messages ยป