# Turn Advisor actions into tickets with Factory Connect a ticket tracker such as Linear, choose where each Advisor action goes, and give coding agents what they need to do the work. Source: https://point11.ai/docs/connectors/factory Updated: 2026-10-31 ## Overview Factory sends the actions [Advisor](/docs/alpha/overview#advisor) recommends to the tools your team already works in: an issue in a ticket tracker such as Linear, or a post in a Slack channel. Each action stays linked to its ticket, so you can follow the work from Point11. Open **Tools > Factory** and choose **Set up** for a guided setup, or set up each part on the page. Factory is free to use. ## Connect a ticket tracker Admins and owners connect a tracker under **Trackers**: choose your tracker's **Connect** button, such as **Connect Linear**, sign in, and approve Point11's access. Your organization connects one workspace of each tracker at a time. The connection belongs to your organization, so it keeps working when the person who connected it leaves. Trackers are connected and disconnected only in Point11's dashboard. **Disconnect** stops everything sent through the connection at once. Its destinations wait until you connect that workspace again, and the issues already filed stay in your tracker. ## Choose destinations A destination is where an action goes: a team in your tracker, where each action becomes an issue, or a Slack channel, where Point11's Slack app posts it. Admins and owners manage destinations and routes. Under **Destinations**, choose **Add destination**, pick **A tracker team** or **A Slack channel**, and name it if you like; otherwise it takes the team's or channel's name. A Slack channel needs Point11's Slack app, the one that brings [Alpha into Slack](/docs/alpha/overview#use-alpha-in-slack), in that channel. Removing a destination removes the routes that send there; what was already sent keeps its history. ## Route actions automatically A route hands every new or revised Advisor action in the areas you choose, or in every area, to one destination. Under **Routes**, choose **Add route**, then its **Destination**, **Areas**, and **Mode**: - **Review and send**: each matching action waits on its Advisor row as **Ready to send** until someone sends or dismisses it. - **Send automatically**: each matching action is sent as soon as Advisor adds it. A route matches an action by its area alone, never by what it says. Pause a route to stop it for a while, or remove it. Each action goes to a destination only once. ## Send an action from Advisor In Advisor, open the menu at the end of an action's row and choose where to send it, such as **Send to Growth (Linear)** or **Post to #web**. Point11 shows the **Title** and **Description** exactly as it will send them; edit either, then send. Editors, admins, and owners can send. When an assistant in Point11 sends an action for you, you approve it first, and the approval names the action and the destination. The **Handoffs** column shows where each action went and its state: **Ready to send**, **Sending**, **Sent**, **Not sent** (with the reason; send it again), **Dismissed**, or **Withdrawn**. **View all activity** in **Tools > Factory** lists every handoff, newest first. ## What a ticket contains A ticket is the action as Advisor wrote it, with nothing dropped or summarized: why it matters, what to do, its acceptance criteria as a checklist, its area and effort, Advisor's estimate of its value when it gives one, and a link to the action's evidence and history in Point11. It ends with a **For coding agents** block naming the action's ID, the MCP tool that reads it, and Point11's MCP server address. ## How tickets stay current Point11 keeps each ticket in step with its action and never overwrites your team's work: - **The action changes in Point11.** The ticket's title and description become the new version. If someone edited them before sending, the new version arrives as a comment instead. - **The action is dismissed**, by Advisor or a person. The ticket gets a comment with the reason, and its handoff shows **Withdrawn**. The ticket stays yours to keep or close. - **Advisor checks your live site.** When Advisor marks the action complete, or reopens it because the problem is still there, the ticket gets a comment with Advisor's reason. Its status stays yours. Each handoff shows its ticket's key, link, and status as your tracker last reported them. A Slack post is sent once and never edited or followed up. ## What Point11 never does in your tracker Point11 reads your workspace's teams, creates issues in the teams you choose, updates the title and description of the issues it filed, and comments on them. It never closes, deletes, or reassigns an issue, never changes its status, and keeps nothing about an issue it didn't file. A ticket's status never tells Point11 the work is done: Advisor checks your live site. ## Coding agents Claude Code, Cursor, Codex, and other coding agents read and update your Advisor actions over Point11's [MCP server](/docs/mcp/overview#connect-an-ai-assistant), signed in as you or with an API key. **Tools > Factory** shows the server address to copy. An agent working a ticket reads the action, its evidence, and how Point11 will check it, then makes the change in your own repository. Point11 never reaches your repository. ## Webhooks for Advisor events To send Advisor's actions to your own systems, admins and owners add an endpoint under **Webhooks** in **Settings > API keys** and choose its events: **Advisor action added**, **Advisor action changed**, and **Advisor action status changed**.