Conecta Archie Send con tu CRM, ERP u otra herramienta con webhooks

What you'll achieve

Let another tool (your CRM, your ERP, your automation or your website) know the moment something happens in your Archie Send account: a new contact, an unsubscribe, a bounce or a campaign that finishes. That way you don't have to copy data by hand or check every so often.

Before you start

• You need permission to manage users on your account (if you don't see Webhooks in the menu Users, ask whoever manages your account).
• Your other tool must have a public address that starts with https:// and receives notifications (in your automation tool it's called “Webhook”; on your website you can create your own route). Local or internal addresses aren't accepted.
• A safe place to store a secret code (for example, your password manager).

Steps

1. Go to Users → Webhooks. Screenshot: Users menu with the Webhooks option and the empty list
2. Click New webhook.
3. Enter an internal Name that helps you recognize it (for example, “Sales CRM”).
4. Paste the Address (URL) your other tool gave you.
5. Choose the events you want to receive. By default they're all selected; remove the ones you don't need. Screenshot: form with events grouped by Contacts, Subscriptions, Bounces and Campaigns
6. Click Save.
7. Your signing secretis shown. Copy it and save it now: it isn't shown again. Screenshot: secret window
8. In your other tool, set up that secret to verify that notifications come from Archie Send (see “How to check the signature”).
9. Back in the list, use the icon Send test. A few seconds later open the History of the webhook: a “Connection test” notification should appear as Delivered.

Expected result

In the list, your webhook appears as Active and, when something happens in your account, your other tool receives a notification. In the History you see each notification, whether it was delivered, how many attempts it took and what your tool replied.

Which events you can receive

• Contacts: created, updated, deleted, blocked.
• Subscriptions: subscribed to a list, unsubscribed from a list, confirmed their subscription (double opt-in).
• Bounces: bounce recorded.
• Campaigns: started, paused, finished, canceled.

Notifications also cover what comes in through imports, public forms and bulk actions, not just what you do by hand.

How to check the signature

Each notification arrives with the X-Archie-Signature header in the form t=DATE,v1=SIGNATURE. The signature is an HMAC-SHA256 of the text DATE.BODY calculated with your secret. Compare it with the one received and discard notifications more than 5 minutes old. The Webhooks screen (section “How do I verify the notification is from Archie Send?”) includes a PHP example for your website.

Each notification has a unique id: if you receive the same one twice, ignore the second. Notifications may arrive out of order.

What happens if your tool doesn't respond

• Your tool must respond with a 2xx code (for example 200) in less than 10 seconds.
• If it fails, we retry up to 7 times over about 21 hours (at 1 minute, 5 minutes, 30 minutes, 2 hours, 6 hours and 12 hours).
• If a notification runs out of attempts it's marked Failed; in the History you can use Resend when your tool is working again.
• If your address fails many times in a row for more than an hour, the webhook pauses on its own so it stops retrying. Fix the problem and click Reactivate.

Common issues

When to contact support

If your tool responds correctly but the history still shows failures, or if an event you expected didn't arrive. Send the webhook name, the event and the approximate time. Don't share your secret.