Connect Jira to Bidsketch

When something happens in Jira, Notis takes the next step in Bidsketch. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Jira to Bidsketch

View example

Review the Bidsketch proposal pipeline

Get a scheduled overview of Bidsketch proposals so pending work is easier to spot.

View example

Track your Bidsketch proposal count

Retrieve Bidsketch proposal statistics on a schedule and include the available count in a run report.

View example

Look up a Bidsketch proposal from a request

Start a webhook workflow with a proposal ID to retrieve its details and return a concise report.

View example

Check a Bidsketch proposal when its Jira issue changes

When a Jira issue changes, retrieve the Bidsketch proposal identified in the issue details and report its status information.

Supported Triggers and Actions

Notis builds workflows that link Jira to Bidsketch. A trigger fires from one place; an action lands in another.

Jira triggers

Bidsketch actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Client

Tool to create a client. use when adding a new client record to bidsketch.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete Client

Tool to delete a client and all their proposals. use when you want to permanently remove a client and its associated proposals from your account.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Delete Fee

Tool to delete a fee. use when a saved fee is no longer needed. use after confirming this fee isn't referenced in any live proposals.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Delete Proposal

Tool to delete a proposal and all its content. use after confirming the proposal id to prevent accidental deletions.

ActionInstant

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.

TriggerInstant

Delete Proposal Fee

Tool to delete a proposal fee. use when you need to remove an existing fee before finalizing or sending a proposal.

ActionInstant

Delete Proposal Section

Tool to delete a proposal section. use when you need to remove a section from a proposal after verifying its id.

ActionInstant

Delete Section

Tool to delete a section. use when you need to permanently remove a saved section after confirming its id.

ActionInstant

Delete Webhook

Tool to delete a webhook. use after obtaining the webhook id to remove it.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.