# Sharing your connector

After you've built your connector, you'll be able to share this connector with others using the share tab.

Sharing tab enabled Sharing console

# Released versions vs Shared versions

Shared Version Released Version
Your connector's shared version is the version which others receive when they install your connector for the first time. When you share a new version, all those who have installed your connector receive an option to update their connectors as well. Your connector's released version is the version all your recipes use. When you release a new version of your connector, all recipes using this connector will use this version immediately.

# Sharing for the First Time

If you are sharing a new custom connector, you will first need to enable sharing in the Share tab. You need to have at least one released version to enable sharing.

Clicking on the "Share version X" button converts the "Share" tab into your new sharing console. This is where you control all the sharing capabilities of your custom connector.

Empty state share tab Empty state


# Sharing your Connector with the Community

There are two ways to share connectors in Workato. You can share your connector with the Workato community or share it with directly with other Workato accounts.

Listing on the community is a quick and easy way to share your connector with all Workato users. They will be able to find and install your connector for use in their own recipes via the community library.

Build Integrations as a Community

Sharing with the community allows other Workato users to automate with your custom connector. This promotes and increases usage of the target application, while simultaneously expands wall-to-wall automation use-cases for everyone.

Find out more about listing custom connectors and best practices.

1

When you list on the community, you'll be asked for the app which this connector connects to. You should select the app that best describes your connector. Simply search for the name of the application you are connecting to and select from a list of apps that Workato has approved.

Select the app that fits best Select the app that your connector is built for

Application name not found

If your application cannot be found, go ahead and type it in plain text!

2

You'll also need to provide some category tags and also choose whether you want to prevent direct installation of your connector. Preventing direct installation allows you to direct people to a landing page of your choice to enquire more about your connector.

TIP

You should only use a logo and provide categories which correspond to the app you are connecting to. In cases where we see otherwise, we may have to disable your listing until it is rectified.

3

Give us a day to approve before your listing can go live on the community. We do this to ensure that all listings on the community are valid.

Find out more about listing custom connectors and best practices.


# Sharing your Connector Privately

Sharing your connector privately can be easily done via a private share link. You can find this in the share tab of your SDK console.

With the sharing link, users can access latest shared version of your connector. They'll be able to view and then install the shared version of your custom connector.

Refresh Sharing Token

You can revoke and generated your sharing token anytime. This allows you to have more control over who has access to your custom connector.

Revoke sharing link Revoke sharing link

Generate sharing link Generate sharing link

# Exporting Packages with Custom Connectors

Recipe lifecycle management is a tool used to export and import entire folders of recipes from a sandbox environment to a production environment in Workato. Often, recipes that you want to export from one account and import into another contain custom connectors that you have built or cloned. When exporting these recipes, Workato helps to export any custom connectors in the manifests as well.

When exporting a manifest, the latest released version and the attached version note of your custom connector that is used in recipes are exported as well. Find out more about exporting here.

# Importing a Manifest with Custom Connectors

When importing a manifest, Workato first checks to see if you have an existing copy of the custom connector. If no existing copy is found, a new one is created with the latest released version as version 1. If an existing copy is found, a new latest version is created instead. In both cases, importing a manifest will immediately release the latest version of the custom connector for you since the recipes you are importing will be using that latest version. Find out more about importing here.

Be sure to explore any dependencies that your existing recipes in your production account might have when importing a manifest that overwrites a connector.

# Frequently Asked Questions

# 1. I've accidentally released an unstable version of my connector. How can I release the last version of my connector again?

Restoring an old stable version of your connector is easy. Simply look through your version history to find the version of your connector that was stable, using the "Released at" column to guide you. Restore that version as your latest version and release it to restore a stable version for all your recipes to run off.

# 2. Why does an autosave occur before the release of a version or use of the debugger console?

Autosaves only occur when there are any unsaved changes to your connector code. This was done to ensure that any last-minute changes you may have made to your code without saving are picked up. It is always advised to test using the debugger console thoroughly before releasing a version.

Packages through recipe lifecycle management are only available on certain plans. While both functionalities can accomplish the migration of your SDK connector, we highly recommend building and testing your custom connector and its associated recipes in your sandbox Workato environment. When you're ready, packages are the fastest way to bring your custom connector(and recipes) from your sandbox environment to production.

# 4. What happens to all my existing connectors that existed before this enhancement?

All existing connectors are backward compatible with this enhancement. They will also contain a list of versions from before the release. You'll be able to see versions since the creation of your custom connector. Creating new versions will require you to release them to use the changes in your recipes.

# 5. I got an update notification, what happens when I update?

Update notifications are always pegged to the latest shared version of its parent connector. Choosing to update always create a new version on top of your custom connector. Be sure to verify that the newly updated connector has changes that make sense to you before releasing it to your own workspace. You can always make edits to the new connector code to suit your purpose.

# 6. How do I know what changes occur across each version and who created that version when working in a team workspace?

Our version history table gives you insight into the actions and triggers present in each version. Our versions table also showcases the user who created a version and who released a certain version. More functionality will come to showcase more fine-grained details about specific changes in the code across versions and the ability to attach notes to different versions. Stay tuned!

# 7. How can I test a specific version of my custom connector in recipes before releasing them to all my active recipes?

We are currently working on improving the coding experience further on the SDK platform to include the ability to run a variety of automated tests on different versions of your custom connector.

In the meantime, a valid workaround would be to create a dummy custom connector that hosts the same code as the latest stable version. You may introduce improvements to this dummy custom connector and test it separately with dedicated recipes. We would suggest testing this new version on copies of both existing recipes that use the custom connector and new recipes to ensure there are no regressions.

# 8. Is there a set way that I should use version notes?

Version notes are meant to be simple ways to communicate information to others in your Workspace as well as to those whom you have shared your connector with. As such, we have made it free-form enough that you may be able to use it as you see fit. Do think about what best practices work best for you! In the future, we plan to introduce additional features that help you build a changelog around your connector. We recommended updating the description of your connector each time you reach a new milestone, such as new actions or triggers.

# Building your custom connector

Now that you're familiar with the platform, its time for you to build your custom connector! Check out our Connector SDK how-to guides.