How it works

Overview - Number Lookup

See the illustration below for an overview of the flow of events when a customer receives a call and the webhook for number lookup is called by the M8Com app.

Overview - Automatic Call Logging

See the illustration below for an overview of the flow of events for automatic call logging. There is an ongoing call between a contact and a user, which is then hung up (by either party), which triggers a call to the webhook end point for automatic call logging, which is then handled by the middleware.

Webhook Setup for customers

Any customer with the Insights add-on can have a Webhook integration setup. The actual setup requires Superadmin permission and is handled by Customer Care. Once the Webhook is set up, the customer can see it and manage it in the Insights settings (Organization Settings / Insights).

There are separate request end points to be set up for number lookup and automatic call logging, with the latter being optional.

Looks like this, from the Superadmin's perspective, when set up:

A Webhook integration can be sorted in terms of priority for number lookup in the same way as any other kind of Insights integration.

Number & custom ID lookup

M8Com calls the webhook automatically in the following cases:

• when the customer receives an incoming call

• when a phone number search is made (as a contact search or in the dialer)

• when presenting items in a call log

• when entering a phone number in number input fields (eg for redirects in IVRs)

• when a caller inputs numeric data via an Input Collector ( optional )

• when a call log item connected to number input is displayed (optional)

Look-up data is cached by M8Com for 2 hours, so any changes made in the integrated system will not be reflected in M8Com. The caching is made to prevent request-flooding of the middleware.

When a response is received from the Webhook integration, the data is presented by M8Com in the same way as it would be for any other Insights integration (eg HubSpot or Upsales). The Webhook icon will be used as a badge to indicate that the number lookup data comes from a Webhook integration.

In the example above, we see look-up information for a contact received via a Webhook integration named "Freshdesk" set up for an M8Com customer. The webhook was called by the M8Com app on an incoming call to the M8Com customer from this contact's number. The Webhook response from the middleware contained information about:

• The contact's name, company, and email address

• A link to the contact's page in the integrated CRM system (Freshdesk in this case)

• Shortcut links for creating activities for the contact in Freshdesk

• A list of recent calls involving the contact and the customer

Automatic Call Logging

If automatic call logging is activated by the customer, the corresponding request end point is called by M8Com each time a relevant call is terminated and a call log item is created. See the specification below for the parameters being sent in the request. It is then up to the middleware to sync this call information with the integrated CRM system.

All phone calls for the customer trigger a webhook request when the call log is created, whether or not a corresponding number lookup request triggered a successful response or not. It is up to the middleware to decide if and how the call is logged in the connected CRM system(s). The customer can configure what kind of calls will trigger a webhook request in the webhook settings (from v2), eg only for calls to certain Answer Groups.

Details & limitations

• The correctness of data and response times for a Webhook integration has nothing to do with M8Com, as M8Com do not control the Webhook implementation.

• Looked-up data is cached and re-used by the M8Com app for 2 hours.

• A webhook request times out after 3 seconds.

Implementation Notes

This specification is for the implementer of a middleware, and describes the request and response formats that must be supported by the middleware.

Notes

It's the responsibility of the Middleware implementer to make sure that the middleware is up and running at all times, and that the middleware is kept up to date regarding any relevant changes to the integrated CRM system(s) (eg API changes).

If a middleware is meant to serve several M8Com customers, the webhook request end point (the URL entered when setting up the Webhook for the customer's M8Com account) set up for a specific customer must contain some kind of ID that can be used by the middleware to identify the customer and route look-up requests to the correct customer account in the integrated system. For example:

Adding is not breaking 🚨

https://M8Com-middleware.provider.com/unique-customer-id

• New fields may be introduced to JSON data models over time and is not considered a breaking change. Integrators must ensure that their integrations ignore unknown fields by default.

Number & custom ID Lookup

REQUEST

With v2 of the API a secret is necessary to setup a webhook integration. The secret will be sent in the authorization header on all requests M8Com makes, contact lookup and call log posting if enabled.

When a number lookup occurs we'll send an HTTP GET request to your request end point. The following will be provided as part of the query string:

Here's an example when a custom ID is ( optionally ) activated.

The request will always contain a "fromNumber", "toNumber" will be supplied when it's applicable. The request will timeout after 3 seconds.

Experimental 🚨

An extra field 'user' is included in the request if the experimental feature "Send user info" is ON (requires Superadmin permission to change). The data provided are subject to change and may differ in the final product.

import express from 'express';

...

// Route matching the URL provided to M8Com
app.get('/M8Com/middleware/lookup', (req, res) => {
  // Validate against  the authorization header
  const { authorization } = req.headers;
  if (!authorization) {
    return res.status(401).json({ message: 'No authorization header provided' });
  }

  if (authorization !== 'Bearer YOUR_SECRET_HERE') {
    return res.status(403).json({ message: 'Invalid secret' });
  }

  // Read query string parameters
  const { fromNumber, toNumber } = req.query;

  // Call your database or API to get the contact information if any
  const res = await queryForContact(fromNumber, toNumber);
  return res.status(200).json(res);
});

...

import express from 'express';

...

// Route matching the URL provided to M8Com
app.get('/M8Com/middleware/lookup', (req, res) => {
  // Validate against the authorization header
  const { authorization } = req.headers;
  if (!authorization) {
    return res.status(401).json({ message: 'No authorization header provided' });
  }

  if (authorization !== 'Bearer YOUR_SECRET_HERE') {
    return res.status(403).json({ message: 'Invalid secret' });
  }

  // Read query string parameters
  const { fromNumber, toNumber, customIdentifier } = req.query;

  // Parse customIdentifier if provided (format: "customId:customValue")
  const [
    customId, // The custom identifier key from a M8Com Input Collector (e.g., "customer_id")
    customValue // The value the caller entered and you can use for lookup (e.g., "1234")
  ] = customIdentifier?.split(':') || [];

  // Call your database or API to get the contact information if any
  // You can now use fromNumber, toNumber, customId, and customValue in your query
  const result = await queryForContact(fromNumber, toNumber, customId, customValue);
  return res.status(200).json(result);
});

...

User ( Experimental )

UserId ( Experimental )

RESPONSE

Example

RESPONSE PARAMETERS

Email

PhoneNumber

Company Info

Field

RESPONSE - ACTIVITIES

moreInfoUrl

A URL leading to a web page with more information about the contact.

"moreInfoUrl": "https://loremIpsum.com/contact/maria-andersson"

Activities

A list of up to 10 activities per type, type has to be one of NOTE, TASK, CALL, TICKET, DEAL.

Activities are sorted by timestamp, newest first.

Note

Task

Call

Ticket

Deal

Appointment

createActivityUrl

A shortcut to the integrated system so that a click on the link leads directly to the Create function for an activity of the specified type (eg a NOTE), for the contact which the looked-up number belonged to.

Markdown

It is possible to style the activity body using markdown. Follow this link for examples on what you can do and how to structure the body. We support most of the features listed, images are not supported and HTML will not be processed only displayed as text.

Example

Example
================
This is a simple markdown document to illustrate different markdown features.  

> #### The quarterly results look great!
> - Revenue was ***off*** the chart.
>>  *Everything* is going according to **plan**.

#### More info  
<https://www.markdownguide.org>

{
	type: 'NOTE',
	...restOfTheNoteData,
  body: MARKDOWN,
  markdown: true,
}

Automatic Call Logging

REQUEST

If auto log calls is enabled a copy with some of the information contained in the call log will be posted to the designated URL.

We'll send an HTTP POST request to your request end point. The event will be in the Content-Type: application/json format:

Request body

Bodysuit

Free text field that will include some of the following sections given that the conditions apply for this call. Every section will be on a new line.

Phone number

Phone number will for the most part be a regular phone number prefixed with country code eg +46 70 123 45 67 . Although in the case that this is a call to a user that doesn't have a real number it'll instead be an ID representing the user.

Username

This will be an email address in the case that the user has one. If the user uses a phone number as username it will instead be the users first name followed by surname.