> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/~/changes/UIUApFI15X6M1wQJrFRy/setting-up-guide/setting-up-flow-builder/integrations.md).

# Integrations

Developers features to integrate the chatbot with any 3rd party softwares

Our Flow Builder is fully equipped for developers to build groundbreaking chatbots in the fastest turnaround time using the visual flow builder. Below are some tools available for developers to streamline the process:

### 1. Triggers from 3rd Party

Picky Assist connectors can receive triggers from third-party platforms and take action to initiate a flow along with the data passed from the platform. You can pass any custom payload, and the same will be available in your flow for personalization.

{% content-ref url="/pages/-MWCBaInEeNqLKh\_NhKx" %}
[Getting Started](/~/changes/UIUApFI15X6M1wQJrFRy/setting-up-guide/setting-up-connector/getting-started.md)
{% endcontent-ref %}

### 2. Webhook Inside Conversation

Whenever a user is in a conversation, it's possible to pass a payload to that specific step of the conversation by posting the payload in JSON format to the endpoint generated by us in the Webhook Step. A common use case is waiting for payment confirmation to deliver your digital product.

{% content-ref url="/pages/RROyebdgjNRYUQsVyF5N" %}
[Webhook](/~/changes/UIUApFI15X6M1wQJrFRy/setting-up-guide/setting-up-flow-builder/steps/webhook.md)
{% endcontent-ref %}

### 3. Trigger HTTP API

You can easily pull information from any other system using the HTTP API step, which allows you to make requests to external APIs.

{% content-ref url="/pages/ew2btUbnmxWvm2mDimco" %}
[Trigger HTTP API](/~/changes/UIUApFI15X6M1wQJrFRy/setting-up-guide/setting-up-flow-builder/steps/trigger-http-api.md)
{% endcontent-ref %}

### 4. Runtime Variable

You can conveniently save the data collected by the chatbots in a runtime variable that can be used only within the flow. Runtime variable data is destroyed when a user exits from the conversation

### 5. Data Lookup

We have a straightforward data lookup to the Picky Assist inbuilt CRM. This helps you to reference a record and progress the flow as per the data saved in another module of the CRM.

{% content-ref url="/pages/T2GEqxFTaqk5eidRM84P" %}
[Data Lookup](/~/changes/UIUApFI15X6M1wQJrFRy/setting-up-guide/setting-up-flow-builder/steps/data-lookup.md)
{% endcontent-ref %}


---

# 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://help.pickyassist.com/~/changes/UIUApFI15X6M1wQJrFRy/setting-up-guide/setting-up-flow-builder/integrations.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.