> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/sign/advanced-features/interactions-and-fields/understand-sign-interactions.md).

# Comprendre les interactions Sign

Les interactions donnent au destinataire la possibilité de compléter des informations au moment de la signature, puis de synchroniser ces données dans Salesforce.

Sur un modèle de document, les objets sur lesquels les interactions sont possibles sont les suivants :

* L'objet principal du modèle de document : par exemple "Opportunité"
* L'objet parent de l'objet principal : par exemple le compte de l'opportunité
* Les objets secondaires configurés sur le modèle de document

Avant de configurer vos interactions, vérifiez la compatibilité des types de champs selon votre niveau de signature :

{% hint style="warning" %}
**Astuce**

A noter toutefois qu'il est possible, pour le signature certifiée, d'utiliser une interaction de type texte pour un champ Salesforce de type nombre ou devise.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://university.gonexa.fr/sign/advanced-features/interactions-and-fields/understand-sign-interactions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.