Public Team Issues Come With Scheduling Ready
Issue created in your public Linear team? The team has a ready-to-use Cal event type for discussing it. No setup delay. Just book.
Trigger
Public Team Issue Created
Fires when a new issue is created in a Linear *public* team. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_CREATED`.
Action
Create team event type
Creates a new event type for a specified team in cal.com; ensure `teamid`, any provided `scheduleid`, `hosts.userid`, and `destinationcalendar` details are valid and accessible.
Why this helps
Public team issues arrive but there's no standard slot to sync on them. You're ad-hoc creating event types or defaulting to group Slack threads that go nowhere.
- Event types exist before sync discussions even happen, reducing friction to book
- Standardizes how the team schedules around issues, reducing confusion
- Public issues get treated with scheduling rigor instead of defaulting to async threads
Setup
Build it in a few focused steps.
- 1Connect Linear and Cal integrations
- 2Create the automation: 'When a new issue is created in the public team, create a team event type in Cal called Sync on Issue [Issue ID]'
- 3Specify team size or other scheduling preferences if needed
- 4Set the trigger to Linear Public Team Issue Created
- 5Test by creating an issue in your public team and verify the Cal event type appears
Questions about this workflow
Should every issue get a sync event type?
You decide. Narrow it down: 'Only create sync types for issues labeled feature or bug', or 'All issues' if you prefer.
What if the issue gets resolved without a sync?
The event type stays in Cal. You can keep it for future reference or delete it. Notis doesn't auto-cleanup based on resolution.
Can the event type name be different?
Yes. Tell Notis exactly what to name it: '[Team Name] Sync', '[Issue Title] Discussion', whatever fits your culture.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Cal. A trigger fires from one place; an action lands in another.
Linear triggers
Cal actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add member to team
Adds a new member to a specified team within an organization by creating a team membership.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add organization attribute option
Adds a new option to an organization's attribute, requiring a display `value` and a `slug` unique for that attribute.
Comment Received Trigger
Triggered when a comment is received.
Delete oauth client webhook
Permanently deletes a specific webhook subscription of an oauth client in the cal application, stopping its notifications.
Issue Created Trigger
Triggered when a new issue is created.
Cancel booking via uid
Cancels an existing and active cal.com booking using its unique identifier (uid).
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Check calendar availability
Retrieves free/busy availability for a specified calendar to aid scheduling without revealing event details; requires an existing, accessible calendar, noting that data granularity can vary.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Check gcal synchronization status
Call this read-only action to verify the connection and synchronization status of a user's google calendar integration with cal.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Check ics feed calendar endpoint
Checks an ics feed url (expected as a query parameter) to verify its validity, accessibility, and icalendar data integrity.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Check Stripe status
Verifies if stripe is correctly connected to the cal scheduling system and functional for processing payments, reporting only on the integration's status.
Connect any two apps with Notis in the middle.
Linear and Cal, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Cal.