Every day at 9am
High priority HubSpot tickets as Linear bugs
Each morning, the agent files a Linear bug for every new high priority HubSpot ticket, with the customer's company and a link back.
HubSpot + Linear integration
Combine HubSpot + Linear and move CRM data into Linear, or issues into HubSpot. Just ask Letaido's AI agent and watch it do the work.
Best HubSpot and Linear integration jobs to start with
Use this HubSpot Linear integration to file bugs and rank requests by deal value.
Every Monday at 9am
Closed-lost reasons as Linear requests
Every Monday, the agent logs each closed-lost HubSpot deal's reason as a customer request on the Linear issue for that feature.
When a request is created
Open deal value on new Linear requests
When a customer request lands on a Linear issue, the agent posts a comment listing that customer's open HubSpot deals and their owners.
Every Monday at 9am
Rank feature requests by open deal value
Every Monday, the agent ranks requested Linear issues by the open HubSpot deal value behind them and comments the list on one issue.
When an issue is marked Done
Tell customers a requested issue shipped
When a requested Linear issue is marked Done, the agent adds a note and owner task to each customer's HubSpot company.
When an issue is marked Done
Launch email list when a requested feature ships
When a Linear issue that customers asked for is marked Done, the agent builds a HubSpot list of those customers' contacts for your launch email.
HubSpot Linear integration options, compared
Linear has no HubSpot integration of its own. IssueLinker and Unito sync HubSpot tickets with Linear issues, Zapier covers fixed recipes, and Letaido covers jobs that need judgement.
| Option | HubSpot tickets into Linear issues | Lost deal reasons into Linear requests | Open deals on Linear requests | Requests ranked by deal value | Picks the matching issue itself |
|---|---|---|---|---|---|
 Letaido AI agent | Yes | Yes | Yes | Yes | Yes |
| Zapier | Yes | Partly | Partly | Partly | Partly |
| Linear's own integrations (built by Linear) | No | No | No | No | No |
Read the full comparison
| Option | Direction | What starts it | Best for | Watch out for |
|---|---|---|---|---|
| Letaido AI agent | HubSpot tickets and deals into Linear issues and requests, and Linear issues that ship back into HubSpot as notes, tasks and lists | A schedule, a Linear event, or when you ask | Jobs that need judgement: matching a lost deal's reason to the right issue, ranking requests by open deal value, filing support bugs without repeats | Not a live two way sync. HubSpot jobs start on a schedule or when you ask, not from a HubSpot event. Linear event jobs need an API key from a workspace admin |
| Zapier | Either way, one recipe at a time: Linear issues from HubSpot tickets, deals, forms and companies, and HubSpot tickets updated from Linear issues | A HubSpot trigger or a Linear trigger. Most HubSpot triggers poll, every 15 minutes on its lowest plan | Fixed recipes, such as a Linear issue for each new HubSpot ticket or each deal stage change | Linear customer requests and customers are available as actions. Choosing the right issue, adding up deal values or ranking needs steps you add and maintain in the recipe |
| Linear's own integrations (built by Linear) | No HubSpot integration is built by Linear. Its customer request integrations cover Intercom, Zendesk and Front, Salesforce, Asks and Slack | Not applicable | Customer requests from support and CRM tools Linear supports | Linear's API and webhooks can connect to HubSpot, but you build and run that yourself |
HubSpot and Linear: the old way vs. Letaido
- 1Filter HubSpot for high priority tickets
- 2Open each ticket and copy its text
- 3Look up the customer's company
- 4Create a Linear bug and paste it in
- 5Paste the ticket link
Every day at 9am, find the HubSpot tickets created in the last 25 hours with priority High. For each ticket with no Linear issue whose title starts with HubSpot ticket <id>:, create a bug in the SUP team titled 'HubSpot ticket <id>: <subject>', with the ticket text and the customer's company in the description, and attach a link to the ticket (my HubSpot account ID is 21457830).
Issue: SUP-88 HubSpot ticket 4483: Annual plan checkout fails with an error
Priority: High
Links: HubSpot ticket 4483
How HubSpot and Linear jobs start
When something happens
A job can start when a customer request is created in Linear or an issue is updated in Linear, like “Open deal value on new Linear requests”.
On a schedule
Saved as an automation, like these jobs: every day at 9am or every Monday at 9am.
When you ask
Type it once in chat.
How to set up the HubSpot Linear integration
-
1Create a HubSpot Service Key
-
2Paste a Linear API key
-
3Approve the first run
Allow all read operations once per app; approve each kind of write once.
-
4Try it in chat first
-
5Choose when it runs
Every HubSpot and Linear action the agent can take
HubSpot
13 groups: 27 reads, 41 writes
- Create and update contacts
- Read companies
- Read deals
- 10 more
Create CRM object · Get ticket · Delete line item · List contacts
Linear
9 groups: 18 reads, 9 writes
- Create and update issues
- Read and write comments
- Admin and advanced
- 6 more
Find issue by ID · Create issue attachment · List projects · List documents
Frequently asked
Does HubSpot integrate with Linear? +
Linear's own integrations don't include HubSpot. With Letaido, its AI agent, Leta, can use HubSpot and Linear in the same job, like filing a Linear bug for each high priority HubSpot ticket or logging a lost deal's reason as a Linear customer request.
How do I connect HubSpot and Linear to Letaido? +
Create a HubSpot Service Key and paste a Linear API key. Then describe the job in chat, or paste a prompt from a job on this page.
Can a change in HubSpot start a job? +
No. HubSpot's own event triggers need a legacy Private App, closed to new accounts, so the HubSpot jobs here run on a schedule you set, or when you ask. An event in Linear can start a job.
Why do Linear event jobs need an admin API key? +
Only Linear admins can create webhooks, so an event job needs an API key from a workspace admin. Letaido creates the webhook for you.
How are lost deal reasons matched to Linear issues? +
It reads the deal's closed lost reason, searches open Linear issues by title for that feature, and picks the one that is the same feature. A deal with no clear match is listed in the chat and not logged.
What stops duplicate Linear bugs from HubSpot tickets? +
It checks first. Each Linear bug title starts with 'HubSpot ticket <id>:', and the job skips any ticket when a Linear issue with a title that starts with that prefix already exists. Don't rename those issues.
Is there a two way sync for HubSpot and Linear? +
Not with Letaido. It runs jobs that read one app and write to the other. For a two way sync, Linear's directory lists HubSpot Sync by IssueLinker (HubSpot tickets and Linear issues) and Unito (Linear and HubSpot).
Will it ask before it changes Linear? +
Yes. Allow all read operations once per app; approve each kind of write once. HubSpot is only read in most jobs on this page, and Linear is where they write.
Put HubSpot and Linear to work today
Connect HubSpot and Linear, then ask for a job like "File Linear bugs for high priority HubSpot tickets". Leta gets it done on your schedule, or the moment you ask.
Get Letaido