> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/community-management/integrations/dev-integration.md). # Dev Integration Connect DEV with Community Management By integrating Dev to CM, you can track your organization's dev community posts and also comments from specific dev users. ### Connect DEV To connect Dev with CM, follow these steps: 1. On the **INTEGRATIONS** page, you will see all the connectors. Scroll down and check the **DEV** connector. 2. Click **Connect**. 3. On the pop-up window, enter the following details: 1. **API Key:** Create a new API key in your DEV account's [settings](https://dev.to/settings/extensions) page. Enter it in on the pop-up window. 2. **Track organization articles:** To track the organization's articles, Copy the slug (dev.to/**slug**) from the organization and enter it. For example: *To track comments from* [*crowd.dev DEV*](https://dev.to/crowddotdev) *articles, you have to insert **crowddotdev***. 3. **Track User Articles:** Enter the user slug to track an individual's comments. 4. Click **Connect**.
{% hint style="info" %} We highly recommend only tracking accounts that are directly related to your company/community. Otherwise, you will potentially pollute your workspace data. {% endhint %} ### Data Tracked Activities * (Nested) Comments on all articles published by selected DEV organizations or users Historical import * No limit Not tracked * Follows of organizations/users --- # 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.linuxfoundation.org/lfx/community-management/integrations/dev-integration.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.