> ## Documentation Index > Fetch the complete documentation index at: https://www.twicecommerce.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # How to send each new order to your CRM > Register an order.created webhook so your CRM, directly or through Make or Zapier, receives every new order with its customer and their checkout answers. > [card] [Open in TWICE Admin](https://admin.twicecommerce.com/settings/connect/integrations) > > settings/connect/integrations Register an `order.created` webhook, and TWICE posts every new order to your CRM, or to Make or Zapier on its way there, with the customer and the answers they gave at checkout. [Webhooks](https://www.twicecommerce.com/docs/concepts/integrations/webhooks.md) explains the payload, the retries and the signature. Keep your leads in the CRM itself. TWICE has no sign-up step ahead of an order and its webhooks carry order events only, so a customer created any other way, such as through the email signup in the storefront footer, sends nothing. A person's first order is the first thing your CRM hears about them. ## Prerequisites > [!WARNING] > > **Required permissions:** > > * **Manage integrations and API keys** (`account_settings:webhooks`), to create the webhook and read its signing secret. Owner and Admin hold it. See [Users & Roles](https://www.twicecommerce.com/docs/settings/users-roles.md). > [!NOTE] > > **Have ready before you start:** > > * **An HTTPS address that receives the events**, such as the address of a webhook trigger in Make or Zapier. TWICE posts only to `https://` addresses. > * **A CRM rule that matches contacts on email.** TWICE keeps one customer per email address, so the same key keeps one contact per person in your CRM. ## The walkthrough **1. Open Webhooks** Open **Settings** in the main menu and choose **Integrations & API** under **Connect** in the settings menu on the left. Scroll past **API keys** to the **Webhooks** section. ![Settings, Integrations & API scrolled to the Webhooks section, with Integrations & API in the settings menu and the Webhooks section highlighted](https://mintcdn.com/twicecommerce/XzdcmB1NxT-YAMjE/images/guide-send-new-orders-to-a-crm-01.webp?fit=max\&auto=format\&n=XzdcmB1NxT-YAMjE\&q=85\&s=03c7e94823812445dbe52f96a56ff50f) **2. Start a new webhook** Click **Create webhook** in the top-right corner of the **Webhooks** section. The **Create webhook** dialog opens on its first step, **Choose event**. ![The Webhooks section with Create webhook highlighted in its top-right corner](https://mintcdn.com/twicecommerce/XzdcmB1NxT-YAMjE/images/guide-send-new-orders-to-a-crm-02.webp?fit=max\&auto=format\&n=XzdcmB1NxT-YAMjE\&q=85\&s=83e00e78c4dafab111c7f7f59b88a267) **3. Choose order.created** Open the **Choose event** list and pick `order.created`, the event triggered when a new order is created. Click **Next**. The dialog moves on to its second step, **Endpoint URL**. ![The Create webhook dialog on its Choose event step, the event list open with order.created highlighted](https://mintcdn.com/twicecommerce/XzdcmB1NxT-YAMjE/images/guide-send-new-orders-to-a-crm-03.webp?fit=max\&auto=format\&n=XzdcmB1NxT-YAMjE\&q=85\&s=23400faaa6769b2968b075712ea1d0ba) **4. Enter the receiving address** Paste your HTTPS address into **Enter URL**. An address that does not start with `https://` shows an error under the field, and **Create webhook** stays greyed out. ![The Create webhook dialog on its Endpoint URL step, with an HTTPS address in Enter URL and no error under it](https://mintcdn.com/twicecommerce/XzdcmB1NxT-YAMjE/images/guide-send-new-orders-to-a-crm-04.webp?fit=max\&auto=format\&n=XzdcmB1NxT-YAMjE\&q=85\&s=475376f8573782f5373765db442894a3) **5. Create the webhook** Click **Create webhook** at the bottom of the dialog. **Webhook created** confirms it, and the table under **Webhooks** lists the new webhook with `order.created` under **Event** and **Active** under **Status**. ![The Webhooks table with the new order.created webhook's row and its Active chip highlighted](https://mintcdn.com/twicecommerce/XzdcmB1NxT-YAMjE/images/guide-send-new-orders-to-a-crm-05.webp?fit=max\&auto=format\&n=XzdcmB1NxT-YAMjE\&q=85\&s=a8330fc612e8498f5f81ab3fb01589a9) **6. Copy the signing secret** Open the menu at the right end of the webhook's row and choose **View signing secret**. Click the copy button beside the secret and give it to whoever builds the receiving side, which checks each delivery's `X-Twice-Signature` header with it. ![The Webhook signing secret dialog with the secret blurred and the copy button beside it highlighted](https://mintcdn.com/twicecommerce/XzdcmB1NxT-YAMjE/images/guide-send-new-orders-to-a-crm-06.webp?fit=max\&auto=format\&n=XzdcmB1NxT-YAMjE\&q=85\&s=78569a61e0a4e4ec4fce5d61d4c88744) **7. Check the first delivery** After the next order is placed, click the webhook's row. Its page lists the `order.created` event, with **Delivered** under **Result** once your endpoint has answered. Click the delivery to read the **Payload** it carried. ## How do I know it worked? * **The webhook is listed** under **Webhooks**, with `order.created` under **Event** and **Active** under **Status**. * **Each new order adds a delivery** on the webhook's page, with **Delivered** under **Result**. * **The payload carries the customer.** Each entry in `data.customers` has the customer's email, name, phone, marketing consent and the built-in fields your checkout asked for, and `attributes` holds their customer attribute answers. Answers to a listing's own questions sit on its line in `data.lineItems`. * **Your CRM shows one contact per email**, updated by each order. ## Troubleshooting / common pitfalls > [accordion] Create webhook stays greyed out > > Use the HTTPS address your receiving side gives you. The address you entered does not start with `https://`, and TWICE posts only to HTTPS addresses. See [Webhooks](https://www.twicecommerce.com/docs/concepts/integrations/webhooks.md#managing-webhooks). > [accordion] Deliveries read Failed, or the webhook reads Disabled > > Your endpoint did not answer with a 2xx status. After three events in a row fail every attempt, TWICE disables the webhook. Fix the endpoint, choose **Enable** in the row's menu, and **Redeliver** a failed delivery from its detail. See [Webhooks](https://www.twicecommerce.com/docs/concepts/integrations/webhooks.md#delivery-and-retries). > [accordion] Your CRM has two contacts for one person > > Match contacts on email in the CRM, the key TWICE matches a returning customer on. A CRM that matches on anything else creates a second contact, and so does a person who orders with a second address. See [Collect customer data at checkout](https://www.twicecommerce.com/docs/guides/customers/collect-customer-data-at-checkout.md). ## Related articles > [card] [Webhooks](https://www.twicecommerce.com/docs/concepts/integrations/webhooks.md) > > Events, payload, retries, the delivery log and signature checks. > [card] [Integrations & API](https://www.twicecommerce.com/docs/settings/integrations.md) > > API keys, webhooks and connectors, section by section. > [card] [Collect customer data at checkout](https://www.twicecommerce.com/docs/guides/customers/collect-customer-data-at-checkout.md) > > Decide what the checkout asks, and where each answer lands. > [card] [API keys](https://www.twicecommerce.com/docs/concepts/integrations/api-keys.md) > > Give the integration that reads TWICE its own key and scopes. > [card] [Custom scripts](https://www.twicecommerce.com/docs/sales-channels/online-store/custom-scripts.md) > > Why purchase tracking runs from this webhook rather than the browser. > [card] [Export customers](https://www.twicecommerce.com/docs/guides/customers/export-customers.md) > > Move a customer segment to an email tool as a file. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.