This webhook can be used to send data when a customer is created or edited.

The webhook runs when:

• a customer is created (if "Create customer" is selected on the webhook)
• a customer is edited (if "Edit customer" is selected on the webhook) and at least one of the following has changed: name, email, address, postal code, city, telephone, mobile, customer group, employee number, SSN, sex, date of birth, newsletter subscription (email or SMS), reminders (email or SMS), journal, remarks, important note, calendar note, customer tags or point program

If "Customers who have said yes to newsletters" is selected on the webhook, it is only sent for customers who have said yes to the newsletter.

The webhook is added to a queue that is processed every 5 minutes. It can therefore take up to about 5 minutes before the webhook is sent.

There is no replacement code that tells whether the customer was created or edited. It is therefore recommended to create one webhook for each action (Create customer and Edit customer) and write the action yourself as text in the JSON, for example "CREATED" or "EDITED".

Example of JSON that can be sent:

The following replacement codes are specific to this webhook and can be used in addition to those in the example:

• [customerExternId] is replaced with the customer's external Id, if one is set.
• [ordersTotalCount] is replaced with the number of paid, non-cancelled online orders on the customer plus cash register receipts.
• [ordersTotalValue] is replaced with the total purchase value including VAT for the orders and receipts above.
• [ordersTotalValueExVat] is replaced with the total purchase value excluding VAT for the orders and receipts above.
• [ordersLastDate] is replaced with the date of the customer's latest order or receipt in the format DD/MM-YYYY. Empty if the customer has none.
• [customerLastBookingDate] is replaced with the date of the customer's latest booking before today in the format DD/MM-YYYY. Empty if the customer has none.
• [customerLastBookingDate_DD-MM-YYYY] is replaced with the same date in the format DD-MM-YYYY.
• [customerLastBookingDate_YYYY-MM-DD] is replaced with the same date in the format YYYY-MM-DD.
• [customerLastBookingService] is replaced with the service on the customer's latest booking before today.
• [customerNextBookingDate] is replaced with the date of the customer's next booking in the format DD/MM-YYYY. Empty if the customer has none.
• [customerNextBookingDate_DD-MM-YYYY] is replaced with the same date in the format DD-MM-YYYY.
• [customerNextBookingDate_YYYY-MM-DD] is replaced with the same date in the format YYYY-MM-DD.
• [customerNextBookingService] is replaced with the service on the customer's next booking.
• [customerNextBookingDateSkipToday] and [customerNextBookingServiceSkipToday] are replaced as above, but today's bookings are skipped, so only tomorrow and later are considered. The date is also available as [customerNextBookingDateSkipToday_DD-MM-YYYY] and [customerNextBookingDateSkipToday_YYYY-MM-DD].
• [customerAcceptsMarketingEmail] is replaced with the status of the customer's consent to marketing by email (0 = no, 1 = yes).
• [customerAcceptsMarketingSms] is replaced with the status of the customer's consent to marketing by SMS (0 = no, 1 = yes).
• [customerTag_begin] [lineBreak] [customerTag_end] is repeated for each customer tag in the system (see Customer tags). The following replacement codes can be used in between:
  • [customerTagId] is replaced with the customer tag's unique Id.
  • [customerTagName] is replaced with the customer tag's name.
  • [customerTagValue] is replaced with the status on the customer (0 = not set, 1 = set).
  [lineBreak] gives a comma between the customer tags.

If the customer's date of birth is not filled in, [customerBirthdateDay_DD] and [customerBirthdateMonth_MM] give the value 00 and [customerBirthdateYear] gives the value 0.

In addition to the replacement codes above, you can freely use replacement codes from the following category to build your own data:

• Customer