Schedule customer meetings from Jira issues
Keep customer requests moving by turning complete Jira meeting requests into Calendarhero meeting requests.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Create Meeting Request V2
Tool to create a new meeting request in calendarhero. use when scheduling a meeting with participants, time range, and additional details.
Why this helps
Customer meeting requests can sit in Jira while someone has to copy the details into a separate scheduling tool.
- Reduce copying between Jira and Calendarhero.
- Keep meeting details tied to the original customer request.
- Skip scheduling when the issue lacks required participant or time information.
Setup
Build it in a few focused steps.
- 1Connect Jira and Calendarhero once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language.
- 3Describe that complete customer meeting requests in new Jira issues should become Calendarhero meeting requests.
- 4Pick the Jira New Issue trigger and choose where run reports go.
- 5Test with one real issue that includes participants and a time range.
Questions about this workflow
Will this schedule a meeting if the issue has no time range?
No. Tell Notis to create a request only when the issue contains participants, a time range, and meeting details, and report when information is missing.
Does this trigger on issues from every Jira project?
No. The Jira New Issue trigger fires only for the project you configure.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Calendarhero. A trigger fires from one place; an action lands in another.
Jira triggers
Calendarhero actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Calendar Connection
Tool to add a calendar integration to a user's account. use after gathering provider credentials.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Contact
Tool to create a new contact. use after confirming contact details before making the api call.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create Meeting Request V2
Tool to create a new meeting request in calendarhero. use when scheduling a meeting with participants, time range, and additional details.
New Project
Triggered when a new project is added in Jira
Fetch Contact
Fetch contact
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Fetch Meeting Details
Tool to fetch details for meetings within a specified timeframe. use this after user provides start and end datetimes in iso8601.
Fetch User Profile
Tool to fetch the profile details of the authenticated user. use after obtaining a valid access token.
List Meetings
Tool to retrieve the user's meetings within a specified timeframe. use after confirming date range to fetch raw calendar data.
List Meeting Templates
Tool to list all meeting templates available for quick scheduling. use after authenticating and when you need to retrieve available templates before scheduling.
Connect any two apps with Notis in the middle.
Jira and Calendarhero, 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 Calendarhero.