KPL-2284
Jira E-mail

Keep Jira and E-mail updated automatically.

Today it sits in a list or a spreadsheet, and afterwards someone retypes it into the system that actually has to act on it. This connector fixes that, and we build it on request: what happens in Jira lands in E-mail by itself, in the shape E-mail expects. Tell us what you need and we agree exactly what should travel.

Notifications
The problem

What this connector takes off your hands

  • Today it sits in a list or a spreadsheet, and afterwards someone retypes it into the system that actually has to act on it.

  • Today nobody notices until someone happens to look. Whatever really cannot wait, you pass on yourself.

What you get out of it

What Jira to E-mail saves you

  • Get a E-mail message for every task you finish in Jira.
  • Get a E-mail message for every new row in Jira.
The link

What travels across the link

Everything this connector moves between Jira and E-mail, and how often.

  1. Notifications

    to E-mail automatically

    From this you get a short message in E-mail in the channel you choose, one line on what happened, so you see it at once without logging in anywhere.

Both sides

What each side expects

Jira and E-mail do not describe the world the same way. This is what has to line up.

E-mail

A notification channel needs to know where the message goes, and only works when one line says what happened.

In four steps

Setting it up

  1. 01

    Request the connector

    Let us know you want to link Jira to E-mail. We get in touch within 24 hours with a timeline.

  2. 02

    We agree what should travel

    Together we settle what should travel out of Jira. A notification channel needs to know where the message goes, and only works when one line says what happened.

  3. 03

    We build and test

    You see the connector run on a few test records before anything becomes final.

What you need

  • An account with edit rights, and the list or project it should land in.
  • Access to the workspace or channel the notifications should land in.

Where it runs

On app.schakel.app, with your own Schakel account. No webshop required.

We build this connector on request. Tell us what you need and we reply within 24 hours.

Common questions

Can you connect Jira to E-mail?

Yes. Schakel connects through the official APIs of Jira and E-mail, so you install nothing on your own server and nothing travels outside those two parties.

Can I choose which events send me a E-mail message?

Yes. You decide which events from Jira produce a message, for instance a new order but not a stock change.

Which E-mail channel do the notifications land in?

The channel you choose. You can also send different kinds of notification to different channels, so it does not become one big stream.

From what moment in Jira does something reach E-mail?

As soon as you add or finish the row or task in Jira that you chose as the trigger, it reaches E-mail.

What does connecting Jira and E-mail cost?

You start free and only pay once the connector is really running. After that the same tiers apply as for any other connector, based on how much runs through it each month.

How often does Jira sync with E-mail?

That depends on your tier: hourly on the free tier up to real time on the unlimited tier. You can always start a sync yourself as well.

Do I get one E-mail message per event or a summary?

By default it is one short message per event, one line on what is happening. If you would rather have a digest, we settle that when setting it up.

What if Jira or E-mail is briefly unavailable?

Nothing gets lost. Schakel retries later and the log shows exactly what happened, so at most you notice something coming through a little later.

Missing something you need?

Tell us what Jira and E-mail should do for you. If it is not in here yet, that is usually because nobody has asked. We build on request and we reply within 24 hours.