> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/integrations/slack-integration.md).

# Slack integration

Guideflow directly integrates with Slack, so you can be notified when a user views a demo. You will receive an instant notification to your configured Slack channel.&#x20;

Empower your sales and marketing teams with instant Slack notifications when a lead interacts with your demo. Monitor engagement metrics like completion rates and steps viewed, and get actionable insights into content effectiveness and audience engagement patterns.&#x20;

### **How to integrate Guideflow with Slack**

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/qp7vwesjp3>" %}

To leverage these features, integrate Slack with Guideflow by following these steps:

* In your Guideflow account, go to the "Integrations" section from the left sidebar.
* Find the Slack integration option and click "Connect".
* Validate your Slack credentials
* Select the Slack channel where you want to receive notifications.
* Choose the specific guideflows for which you desire notifications.

Upon completing these steps, your selected Slack channel will receive notifications every time a user views a demo.&#x20;

This integration ensures that your sales and marketing teams are constantly updated, enabling them to react swiftly and effectively to prospect interactions.


---

# 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://docs.guideflow.com/help/integrations/slack-integration.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.
