# Example with 1 decision rule

Let's say that you are creating a **Database -> HubSpot** and you have companies store in the following table and want to send this data to HubSpot Companies using the name as key to know if the current company in the database is already present in HubSpot:

| ID   | Name     | City  |
| ---- | -------- | ----- |
| 1234 | Acme Ltd | Milan |

We can build our decision rule like this:

IF \[ **Company Name** ]\
\= 0: **ADD**\
\= 1: **UPDATE**\
\> 1: **STOP**

This decision rule can be read as:\
If you search in HubSpot for "Company Name" equals to "Acme Ltd." and you **find 0 results**, then add the record as new object using the "Database mapping" as translation layer. If you find **exactly 1 result**, update it. If you find **more than 1 results**, skip this record and go to the next.

You can concatenate more than one decision rules, they will be evaluated in cascade using the "NEXT" decision to jump from one decision rule to the next one.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.erpbridge.io/the-operation/3-decision-rules/example-with-1-decision-rule.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.