Saltar al contenido principal
Eva asks your system about the customer who is writing, by phone number. In Customer purchases you enter the name each detail has in your system’s response, so Eva can find that customer’s purchases.

What you will achieve

You will save, in the Custom API connection, the names your system uses to return a customer’s purchases, without writing JSON.

Requirements

  • The owner or admin role in the Eva account.
  • A Custom API connection already created in Settings > Integrations.
  • A sample of the response your system gives when it looks up a customer. Ask whoever manages that system.

Enter where the purchases are

1

Open the connection

In Settings > Integrations, open Custom API. On your connection, open Customer purchases.
2

Turn the lookup on

Turn on Eva looks up the customer’s purchases in this system. Purchase list and Purchase number appear, the two required details.
3

Enter your system's names

In each field, enter the name that detail has in your system’s response. Use dots for a detail inside another, for example customer.orders.
4

Confirm whose purchases they are

Turn on The response only has this customer’s purchases if your system answers with the purchases of one customer. If each purchase carries its customer, enter that detail in Customer of the purchase, under More purchase details. A purchase list inside the customer, for example customer.orders, also counts. Without one of the three, Eva does not use the purchases. With the switch on, the response must also carry the id of the customer Eva looked up; if it carries another customer or several, Eva does not use the purchases.
5

Add the products and more details

In Products in each purchase, enter the product list, the SKU and the quantity. The product name and the unit price are optional. More purchase details has the total, the currency, the status, the refund status and the purchase source.
6

Save

Select Save.
To stop Eva from looking up purchases, turn off Eva looks up the customer’s purchases in this system and select Save.

How to know it worked

Under the fields, Eva describes what it will read in one sentence, for example: “Eva reads the purchases in “orders” and identifies each one by “number”.” When you open the page again, the fields are still there.

If something goes wrong

  • A field says “Use letters, numbers, hyphens and dots”. That name has a space, a bracket or another symbol. Enter only the name of the detail, with dots between levels and four levels at most.
  • A field says “Fill in this detail”. The purchase list and the purchase number are required. If you enter the product list, the SKU and the quantity are required too.
  • The block says “Custom”. The connection has a map set up through the API in a format the form cannot read. Eva keeps it as it is.
  • Eva does not mention the purchases. Check that The response only has this customer’s purchases is on or that Customer of the purchase has a value. Check too that the names match your system’s response.

Next steps

Send an opportunity's products to your system

Track your sales in the pipeline