Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


Overview

If you are developing for Atlassian Marketplace it has a very good Vendor Management portal with an Open API to pull data from. This portal might be a better source of data for your Accounts in journy.io as opposed to your CRM or could journy.io might be a way for you to get proper CRM as a result of tight integration.

Let’s try to work it out!

Pre-requites

If you have engineering team in place and they are available:) you can task them with pulling data from Atlassian Marketplace API on sequence and using journy.io API to connect.

The reality is engineering teams are rarely available and/or you might want to POC it before make a commitment to assign you engineering team on it so you develop something you would need to maintain and evolve in the future.

Therefore we will be using No-code solution like Make.com in this guide plus share some ready to use blueprints. But you can do it with any other platform you are proficient in.

We will be also using message bus like Segment.com, just because Make.com has a good integration with Segment plus journy.io are fully compatible with it. This will also give you long term possibility to change journy.io with another tool and/or send same data elsewhere.

Configuring Segment Source

Login to you Segmen account and click Sources > Add source

Type API in search and select HTTP API source to add

image-20240605-121653.png

Click Add source

image-20240605-121732.png

Put some good name and click click Add source

image-20240605-121839.png

That’s it - now you have where to upload data with make.com

Configuring Segment Destination

Let’s connect now this Segment source with journy.io.

Logging to your journy.io account and click on Connections > Add connection

image-20240605-122615.png

Select Segment

image-20240605-122705.pngimage-20240605-122741.png

Segment connection will open up. Select on Source tab and click on Api key to copy it

image-20240605-122922.png

Go to Segment and choose Destinations > Add destination.

Search for journy and select it

image-20240605-123115.pngimage-20240605-123145.png

Select your Source and click Next

image-20240605-123458.png

Put some good name and select Create Destination

image-20240605-123618.png

Click on Api Key

image-20240605-123743.pngimage-20240605-123809.png

And copy the key from journy.io that should be still in your Clipboard. Otherwise switch to journy.io and copy it again

image-20240605-122922.pngimage-20240605-124002.png

Good - now you have Segment fully configured to receive data from No-code tool mike make.com and push into journy.io

Let’s now play with make.com

Make.com blueprint

Login to your make.com account.

Click Scenarios > Create new scenarios

Select More > Import Blueprint

image-20240605-124525.png

Import the Blueprint Attached

image-20240605-124614.png

Your Atlassian vendor data

Click on Atlassian Marketplace Access Properties and specify your Vendor ID

image-20240605-124936.png

Your Atlassian authorization token

Navigate to https://id.atlassian.com/manage-profile/security/api-tokens

Click Create API token

image-20240605-125332.png

Copy your access token

image-20240605-125418.png

Navigate to https://www.blitter.se/utils/basic-authentication-header-generator/

Put your email (the same you used to generate token) as username

image-20240605-125723.png

and token as password to Generate Header

image-20240605-125828.png

Copy Authorization Header generated. Should be “Basic ….

Get back to Make.com and insert it into Atlassian Marketplace Access Properties

image-20240605-130137.png

Almost there!

Your Segment write key

Go to your Segment account and select you Source

image-20240605-130254.png

Copy your Write Key

image-20240605-130342.png

Go back to make.com and open Segment Access Properties and paste it there

image-20240605-130527.png

You are there!

Making it work

You did all the work to start pulling your data from Atlassian Marketplace and pushing it to journy.io. We suggest to start with 1-2 test Licences/Accounts before upload in bulk and making it business as usual.

Test account

Before go all-in with integration you might want to test it out with 1-2 test account/licences. Go to your Atlassian Marketplace Vendor Portal and get 1-2 Entitlement Numbers for test licences you want to process

Go to Make.com and click on Atlassian Marketplace Access Properties

Put test Entitlement Number into respective property and assure that AppKey and LastUpdated are empty

image-20240605-145334.png

Click Run once

image-20240605-145545.png

If all good you will see all labels green

image-20240605-145718.png

Also by clicking on execution counters you can trace end to end execution on all the steps.

Let’s go to Segment, select our Source and click Debugger tab to assure the message was sent

image-20240605-145931.png

and finally let’s go to journy.io to check our Account created/updated

image-20240605-150043.png

All active accounts

Once you tested it with 1-2 test licences you have 2 options:

  1. Bring all active accounts and move into https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/edit-v2/2774433793#Final-configuration-in-journy.io

  2. or do https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/edit-v2/2774433793#Final-configuration-in-journy.io and see how it works to for 1-2 accounts before uploading all active

Let’s bring all active licences to journy.io from Atlassian Marketplace.

Come back to your scenario in make.com (or any other No-code platform).

Click on Atlassian Marketplace Access Properties

  • Clear Entitlement Number

  • Specify your AddonKey (in case you want licences to a particular App)

  • Specify active in status field

  • Clear Last Updated if you have it

image-20240606-070753.png

Click Run once

If all good you will see all labels green

image-20240606-071122.png

Plus you can verify the amount of accounts/licences created.

Let’s go to Segment, select our Source and click Debugger tab to assure the message was sent

image-20240606-071248.png

and finally let’s go to journy.io to check our Account created/updated

image-20240606-071544.png

Now you have all your active accounts in journy.io

Make it business as usual

Information at Atlassian Marketplace is updated regularly and you want all the change replicated in journy.io to have up to date look at your clients. To make it happen we will configure an option to execute scenario on cadance and solicit only updates from Atlassian Marketplace.

Come back to your scenario in http://make.com (or any other No-code platform).

Click on Atlassian Marketplace Access Properties

  • Clear Entitlement Number

  • Specify your AddonKey (in case you want licences to a particular App)

  • Clear status

  • Specify Last Updated to make it yesterday for e.g. (if you want to run it daily)

{{formatDate(addDays(now; -1); "YYYY-MM-DD")}}
image-20240606-072209.png

Click Run once and assure you get it in Segment and updated in journy.io

Now turn on scheduling and select a time of day you want to execute it.

image-20240606-072520.png

Click Save.

You can check progress of execution anytime by clicking on History tab

image-20240606-072749.png

Final configuration in journy.io

blah blah

Suggestion on Business Settings

blah blah

Suggestion on Stages Configuration

blah blah

What’s Next?

What else you can pull from Atlassian Marketplace?

blah blah

What are the next steps with journy.io?

blah blah


Tip: Need help with your Connectors?

Reach out to our support team

https://releasemanagement.atlassian.net/servicedesk/customer/portal/14

or book time to make it together

https://calendly.com/journy-io/meet-us?back=1&month=2024-04
  • No labels