> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/best-practices/integrating-secoda-into-existing-workflows.md). # Integrating Secoda into existing workflows Check out best strategies on integrating Secoda into your current day-to-day flows. Let's face it - bringing on a new tool to your already-hectic workflow can seem stressful. With Secoda, users shouldn't have to change current behaviors to engage with the product. We've iterated on and added many features to allow Secoda to seamlessly integrate with your existing workflows. ### [Secoda's AI Slackbot](/extensions/slack-connection/slack-user-guide.md#secoda-ai-slackbot) * Connect the AI Assistant to your data requests Slack channel so that users don't have to leave their Slack workflow to find answers. Check out [best practices ](/best-practices/slack-less-than-greater-than-questions-workflow.md)here. * End result: * Improved data literacy * Reduced time spent on repetitive replies to users * More time for analysts to focus on their most important tasks ### [Chrome](/extensions/chrome-extension.md) * Download the Chrome extension to enable your users to access Secoda metadata directly in the other tools they're currently working in, like BigQuery and Tableau * If the extension is enabled, a user can see and edit important information like ownership and descriptions coming from Secoda without having to move across multiple tabs ### Enable [Notifications](/features/notifications.md#slack-notifications) * Users can pick and choose notifications and alerts regarding changes in the workspace to be sent over Slack * If you own or subscribe to a resource, you will receive notifications regarding any changes to the schema - indicates it might be time to edit documentation or edit a dashboard * End result: * Improved data quality * Reduced time spent on manual notifications ### [Jira](/extensions/jira.md) Integration * Connect the Jira integration to seamless manage your data requests coming in from Jira, directly in the Secoda Questions feature ### [Confluence](/extensions/confluence.md) Integration * Connect the Confluence integration to bring in content from Confluence spaces and pages * Why integrate Confluence? * Users don't have to change their current behavior of documenting there * Documentation from Confluence becomes easily searchable within Secoda, as well as from Slack after you connect the Slack integration * Ask the AI assistant questions about what exists in Confluence to speed up documentation and discovery * Link documents to related resources like tables in the Catalog, or metrics in the Dictionary --- # 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.secoda.co/best-practices/integrating-secoda-into-existing-workflows.md?ask=&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.