Rich Birks
18th October, 2023
Jira
Confluence
Bitbucket
The latest addition to your ScriptRunner toolbox
Imagine for a moment that saying “Of course” to integration requests doesn’t immediately have you breaking out in a sweat. Make it a reality with this new tool.
“Of course we can.”
How often do you say these words with genuine joy? Without a little pit in your stomach that gains strength the more you think about the task that’s being presented to you?
Let’s imagine someone approaches you and they want to connect the engineering team’s Jira and the UX team’s monday.com boards.
“Of course we can.” you say, as long as you don’t want something complicated…
At certain moments, they’d like to have something automatically noted on Confluence, and at others to have a ticket created in ZenDesk for the customer satisfaction team to follow up on, can we do that?
It’s going to take me three weeks and five subscriptions to do but… “Of course we can.”
Oh, and when a document is added to the approved folder in Dropbox, they also want an email notification to trigger for the legal team, is that okay? Can we manage all of that?
“...Of course we can.”
The answer is always of course.
The tricky part of keeping our colleagues and clients happy is that meaningful integration isn’t always easy.
Why are integrations harder than they need to be?
Most integration apps in the Atlassian space are designed to address very specific – and often simple – use cases. As long as the triggers are straightforward and there’s no sprawling branching logic, you’ll be able to find a low-code point-and-click integration tool on the Atlassian marketplace. And while these tools tick the box for uncomplicated, no-frills integrations, when it comes to more complex needs, such as multi-app syncing, migrations on live systems, or consolidations of multiple instances? You’re out of luck.
As a result of these shallow integration solutions, you end up needing to combine several (each with its own interfaces, licences, etc.) to solve the not-so-simple problem you were trying to tackle.
When working with Atlassian tools, it can also be tricky to find solutions which comfortably reach outside of Jira, Confluence and Bitbucket into other toolsets.
And, of course, the more integrations you have, the higher the licensing costs, the greater the complexity, and the more headaches you sign yourself up for. In addition to the pain of paying more, there’s the additional documentation requirements, poor visibility and centralisation of what you’re building, upskilling on each and every new tool in the integration stack, and the energy you drain by having to monitor all eleven technologies that you’ve got running to pull off what you needed.
The situation becomes even more daunting when you have to manage and keep track of multiple integration tools for multiple clients. Maybe you’re a consultant, or you’re an admin serving several internal teams with different needs. With no central place to view and manage all the moving parts, you find yourself switching back and forth between different instances and apps all day long.
Every time you log on, you have to refamiliarise yourself with that app's unique rules engine, workflow builder, and bespoke UI. It can feel like starting over every time, like being stuck in an endless groundhog day loop.
The result? Overwhelm, confusion, frustration.
Does it have to be like this?
We sure don’t think so.
Imagine for a moment that saying “Of course” to integration requests doesn’t immediately have you picturing all of the possible pitfalls and sidequests you might encounter on your journey of trying to make it happen. That feeling of peace, of achievement?
You can get it with a new tool available from the ScriptRunner team. It had us saying a fond farewell to all of our other integration tools (and the mental pictures of our avatars leaping over spikes and trying to climb over walls with a rope that’s too short).
Introducing ScriptRunner Connect
ScriptRunner Connect is a new all-in-one, code-first integration solution for Atlassian and beyond. Here’s why it’ll have you saying goodbye to your existing tools, too:
1. Why pay for twelve tools when one can do it all?
One login gives you access to all the infrastructure and pre-built connectors you need to integrate Atlassian apps with popular software from the likes of Microsoft, Google, ServiceNow, and more.
With ScriptRunner Connect, you can consolidate and organise all of your integrations (yes, even the really complex ones) in one neat place. Since all the infrastructure is handled for you, you can focus on developing innovative solutions without having to worry about hosting, security, or scalability.
Erko Knoll, Lead Engineer for ScriptRunner Connect says: "ScriptRunner Connect does the heavy lifting when it comes to building integrations so you can focus on building your business logic—where your expertise is most valuable. It makes the processes and tools engineers have used for years accessible to all."
(Psst! You can see ScriptRunner Connect in action during this recorded webinar!)
2. Get complete control of how your tools interact with each other
ScriptRunner Connect uses a code-first approach to give you complete control of how your integrations work. No more point-and-click half-hearted solutions. Here are a handful of the features that make ScriptRunner Connect a dream to use:
- JavaScript/TypeScript assisted coding environment
- Managed connections: authenticate once (in just a few clicks), then sit back and let the app handle the rest
- Managed APIs: rapidly learn new APIs and reduce long API calls to a single line
- NPM package manager: pull in your favourite code when and where you need it
- Environments: easily manage deployments between UAT and production
With a code-based tool like ScriptRunner Connect, the possibilities are truly endless. Solve the most complex integration challenges without the pain, time, cost and risk of developing bespoke solutions.
3. You can literally connect to anything
Anything with an open API can be integrated using ScriptRunner Connect, even if we haven't got a managed connector for it. You can build your own using our generic (ie. custom) HTTP connector.
Our favourite example so far is someone who set up their smart lighting to change colour whenever an SLA was about to be breached...
4. Others are already loving it
Beta users of ScriptRunner Connect bowled us over with feedback like this:
"We used ScriptRunner Connect to migrate Tempo worklogs from one cloud instance to another. It saved us from going down the CSV or individual API call routes, which would be a manual nightmare. We found it really easy to use, but if we needed support, ScriptRunner Connect's lead engineer, Erko Knoll, was always available to help. Our client couldn't be happier with the result— we can't wait to try out more use cases. Excellent work in every respect."
-- Nathan Ellis, Principal Atlassian Consultant, Contegix
Want to hear about how others have been using ScriptRunner Connect already? Read this case study.
5. Unrivalled ScriptRunner support and inspiration
If you already use ScriptRunner for Jira or Confluence, you won’t be surprised to hear that our tools come with best-in-class engineering and support. We’re churning out connectors, tutorials and templates to help you deliver a connected landscape fast.
6. There's a free forever plan
A no-barriers way to try it out for yourself today.
ScriptRunner Connect started life over in Adaptavist, also part of The Adaptavist Group. We’re delighted to be bringing it now into the ScriptRunner family to help you connect (sorry not sorry) your Jira, Confluence and beyond!
Try it free today
There's a free-forever plan so you can explore to your heart's content.
Get a tour
Watch this introductory webinar (recorded on Wednesday 8 November) to see how ScriptRunner Connect works and what you can do with it.