Saltar al contenido principal
A CRM action sends an opportunity’s data to your system. The action’s product list sends each product with the keys your system expects.

What you will achieve

You will create or edit an action that sends an opportunity’s products, without writing the JSON body by hand.

Requirements

  • The owner or admin role in the Eva account.
  • A Custom API connection already created in Settings > Integrations.
  • The field names your system expects for each product. Ask whoever manages that system.

Set up the product list

1

Open the actions

In Settings > Integrations, open Custom API. Go down to CRM actions.
2

Choose the action

To change a saved action, select Edit on its row. For a new one, fill in Internal name, Visible label and Path.
3

Turn the list on

Open Product list and turn on Send the opportunity’s products. Three details appear: SKU, quantity and unit price.
4

Enter your system's keys

In List key, enter the name your system receives the list under. On each row, enter your system’s key and choose the product detail. To add another, select Add detail.
5

Save

Select Create CRM action or Save changes. The JSON body shows the same list.
On a saved action, the connection, the record and the internal name cannot be changed.

How to know it worked

Under the rows, Eva describes the send in one sentence, for example: “Each product on the opportunity sends the SKU, the quantity, and the unit price in “products”.” When you open the action again with Edit, the rows are still there.

If something goes wrong

  • The list says “Custom”. The JSON body has a hand-written list the rows cannot show. Eva keeps it as it is; edit it in JSON body.
  • The opportunity shows “Missing SKU for” and a product’s name. That product has no SKU and the action needs it, so nothing was sent. Fix the product on the opportunity and select Retry.
  • The opportunity shows “The external system answered” and a text. That text is the reason your system gave. Fix what it says and select Retry.

Check the status of the record in your system

An action that creates a record in your system, such as a presale, can check its status later. The action needs the External ID path, because Eva checks the record with that ID.
1

Open the action

In CRM actions, select Edit on the row of the action that creates the record. The action uses the POST method.
2

Turn the check on

Open Check status and turn on Check the status from the opportunity. Eva suggests the action’s path followed by {{link.external_record_id}}.
3

Write the path and the field

In Path to check, keep {{link.external_record_id}} where the ID goes. In Status field in the response, write the field’s name, for example status.
4

Save

Select Save changes. Below the fields, Eva describes in one sentence the check it will make.

Refresh the status from the opportunity

On the opportunity, the record the action created shows its status and the Refresh button. When you select it, Eva asks your system right then and shows the status exactly as it comes, with the time of the check.
  • “Status: not checked yet” means nobody has checked that record yet.
  • If the check fails, Eva keeps the last status and explains the reason below it, for example “not found in the system”.
  • “no access to the system” means the connection lost its access. Reconnect it in Settings > Integrations.

Next steps

Track your sales in the pipeline

Automate repeated tasks