Using Integrations

​

Assistant Configurator

Within the assistant configurator, create an assistant that should be able to use the integration. You can use the guide on creating an assistant to learn more about creating great assistants.

​

Adding actions

Within the assistant configurator, you can now add actions of the integrations enabled in your workspace.

Search and select the action of your choice and add it to your assistant by choosing either an individual connection or a preselected connection.

Default connections allow you to connect your own account, in that case, your own Google Calendar account, and let the assistant act with your access rights, resources, and constraints within the connected application. This option requires you to add an OAuth connection either when trying to trigger an action of this integration for the first time, or via the integrations menu. Throughout the OAuth dialogue, select the account you want to the assistant to execute the action in, and allow the access requested by the Langdock integration.
A preselected connection can be chosen by all users of this assistant when using this action, which requires additional attention regarding access rules.

After adding the action, you can select whether its execution requires your confirmation, or can be triggered automatically by the assistant. In the first case, the assistant will always prompt you with the action and its preselected input parameters, before calling that action.

​

Using actions

Now you can use integration within your assistant. From the context of the conversation, the assistant will trigger actions automatically. If an action requires confirmation, you will be prompted with the concrete request, including input parameters, the model wants to execute. Pressing allow will trigger the action.

​

Usability recommendations

​

Adding actions to an assistant

When thinking about which actions to add to an assistant, we recommend to be a bit generous here. Some integrations have actions that collect relevant context information, like the Get deal context action in HubSpot, which gathers information about internal ids, in this case for available pipelines and stages, which enables you to use other actions like Create deal or Update deal easyer. If this action is added you can ask the assistant to get all existing pipelines in you workspace, and the specify in natural language which ones a new deal should be added to. The alternative would be to get this information from your HubSpot settings.

​

Actions requiring confirmation

In general, we recommend all actions that collect, download, search, or read information to require no confirmation. This allows the assistant to be faster at gathering all required information without doing much harm. For actions that create, update, or delete objects, requiring a confirmation allows you to check the parameters generated by the model and make sure the intended action is performed.