What Linear is and how Kite uses it
Linear is the issue tracker and project planner many software teams use to run product work. Every bug fix and feature lives as an issue, issues roll up into projects with target dates, and teams work in cycles, which are Linear's name for sprints. An AI marketing agent can use Linear in two ways. It can read what the product team is shipping and turn it into marketing, and it can track the marketing team's own work in the same place engineering already looks.
Kite does both. It reads closed issues and project updates to find what's worth announcing, writes and publishes the announcement, and records the marketing work as Linear issues and projects. You connect your own Linear account to get started.
Marketing jobs Kite can do with Linear
Linear holds the most reliable record of what your company is building, and Kite treats it as the source for launch and release marketing. The jobs below follow that work from the features that just shipped, to the ones coming next, to the marketing tasks that come out of both, and finally to the customer feedback marketing sends back to product.
Turn shipped issues into release notes and launch content
Kite reads the issues your team has moved to Done and writes the announcements those changes deserve. Picture a cycle that closes on Friday with fourteen finished issues. Kite reads each issue's title, description, labels, and comment thread, and it downloads attached screenshots it can reuse. Then it sorts the changes customers will notice from the internal fixes they won't.
From there, Kite writes the release notes in your brand voice. It explains each change in terms of what a customer can now do, not how the code changed. The same material becomes a short email to existing customers and a LinkedIn post about the biggest improvement. Once you approve them in Slack, Kite publishes the changelog page on a site it hosts or through your connected CMS, sends the email, and posts to your connected social accounts.
The last step happens back in Linear. Kite adds a comment to each announced issue and attaches a link to the published post, so anyone who opens the issue can see how it was announced.
Plan launch marketing around what's coming next
Kite reads your Linear projects to see which features are close to shipping and when. Each project carries a target date, milestones, and the status updates your team posts, including whether the project is on track, at risk, or off track. Kite uses that schedule to start launch work early enough to be ready on the day.
Say your Salesforce sync project has a target date three weeks out. Kite proposes a launch plan in Slack: the buyer questions the feature answers, a landing page, a comparison page against your closest competitor, an announcement email, and posts timed around the ship date. If the next project update marks the work at risk and the date slips, Kite moves the launch plan to the new date and tells you in Slack.
For larger themes, Kite reads Linear initiatives, which group related projects under one company goal. A quarter's worth of reporting features can then become one story for a campaign instead of five separate announcements.
Track your marketing work as Linear issues and projects
Kite can put marketing work into Linear so your team sees it next to everything else. When you approve a launch plan, Kite creates a project for the campaign and adds milestones with target dates, such as the landing page going live and the email going out. It files an issue for each piece of work. Each issue gets a clear title, a description of what done looks like, an assignee, a priority, a due date, labels, and a place in the right cycle.
Kite keeps those records current as the work moves. When the landing page is published, Kite moves the issue to Done and comments with the live URL. When the campaign hits a milestone or runs late, it posts a project update so anyone following the project sees the status without asking in Slack. If one task can't start until another finishes, Kite marks the first issue as blocked by the second.
Send customer feedback from marketing to the product team
Kite hears what prospects and customers ask for in Slack threads and in email to your team's Kite address, and it can bring that feedback into Linear. Say three prospects in one week ask whether you integrate with Pipedrive. Kite searches Linear for an existing issue about it. If it finds one, it adds a comment that summarizes the requests and who made them. If it doesn't, it files a new issue on the product team with the evidence attached and links it to related work.
That gives the product team a running count of demand from real buyers. It also gives Kite a reason to come back later. When that issue closes, it's one of the first things Kite announces, starting with the prospects who asked for it.
What Kite reads and changes in Linear
Information Kite can read
- IssuesKite reads each issue's title, description, state, priority, labels, assignee, project, cycle, due date, and timestamps, and it searches issues by keyword. This is how it finds what shipped and what's still in progress.
- Comments and attachmentsKite reads the discussion on an issue and downloads attached files such as screenshots, which add the context and visuals an announcement needs.
- Projects, milestones, and project updatesKite reads project target dates, milestones, and the status updates your team posts, including each project's health. That schedule tells it when to start launch work.
- CyclesKite reads each team's cycles, including the active one, so it can gather everything a cycle finished.
- Initiatives and saved viewsKite reads the initiatives that group related projects, and it reads the issues in a custom view your team has already set up, such as a view of customer-facing changes.
- Teams, workflow states, labels, and peopleKite reads how your workspace is organized, so it files work on the right team, uses your existing states and labels, and assigns issues to the right person.
Information Kite can create or change
- IssuesKite creates issues with a title, description, assignee, priority, due date, labels, project, and cycle. It updates them as work moves, archives the ones no longer needed, and marks one issue as blocking, duplicating, or related to another.
- Comments and attachmentsKite comments on issues and edits or resolves its own comments. It also attaches a link to an issue, such as the published release notes.
- Projects and milestonesKite creates projects for campaigns and launches, adds milestones with target dates, and updates a project's name, description, dates, state, or lead.
- Project updatesKite posts status updates on a project, with a health status, and edits them when the picture changes.
- Labels and initiativesKite creates labels, such as one for launch-ready work, and it can create and update initiatives through the API key connection.
How Kite connects to Linear
You can connect Linear in either of two ways, and both require your own Linear account. The first is OAuth: connect your Linear account through OAuth, and Kite then works with the teams, projects, and permissions available to that connected account. This route covers the most ground, including cycles, milestones, project updates, attachments, and labels.
The second is an API key: add an API key for your Linear account, and Kite uses the access granted to that key. Both routes let Kite read and create issues, projects, and comments, and update issues. The API key route also gives Kite direct access to initiatives and your saved views.
Once Linear is connected, tell Kite which team holds your product work and which holds your marketing work, if that's a separate team. Kite reads the workflow states and labels each team already uses, so new issues fit how your team already works.
Where Linear fits in Kite's marketing work
Linear supplies the facts and the timing for a launch. Kite reads the project's target date and status to know when to start, reads the finished issues to know exactly what's shipping, and writes the launch page, email, and posts from that record. During the launch, Kite can track the marketing tasks as Linear issues, and afterward it links the published work back to the issues it announced.
Limits and product-specific details
- Kite sees what the connected account sees. Kite works in the teams, projects, and issues visible to the Linear account or API key you connect. A private team stays out of reach unless that account belongs to it.
- Work appears under the connected account. Issues, comments, and project updates Kite writes show up under the Linear account you connected. Some teams connect a dedicated account for Kite so its work is easy to recognize.
Common questions
Can Kite write release notes from Linear every week on its own?
Yes. Ask Kite to make it a recurring job, such as every Friday afternoon. Each week it reads the issues closed since the last run, drafts the release notes and any posts worth sending, and brings them to the Slack channel you chose for approval.
Can Kite work across our product and marketing teams in Linear?
Yes. A connected account usually sees several teams, and Kite treats them differently. It reads the product team's issues and projects to find what's worth announcing, and it files and updates the marketing team's issues for the work it does. Each team keeps its own workflow states and labels, and Kite uses the ones that belong to each team.