Articles in this section

Create an integration

Creating an integration gives you an empty container on the Home page where you can add the flows, APIs, tools, and topics for one business process and manage them together. This article is for anyone with Manage all permissions who is setting up a new custom integration; it takes you from the Home page to a named integration ready for its first flow, and then shows you how to describe the integration for the other people who'll work in it. For what an integration is and how it's organized, see Integrations overview.

Prerequisites: You must have Manage all permissions to create an integration. See Manage user roles & permissions to an account.

Create an integration

  1. Go to Home home-icon.png.
  2. At the top right, select Create > Integration.
  3. Enter a Name and, optionally, a Description.
  4. Select Save.

The new integration opens on its Flows tab, and from now on it appears on the Home page. To add content to it:

You can move a flow or API into a different integration at any time; see Move a flow to another integration.

Edit the name, description, and readme

The Admin tab holds the integration's name and description and a readme. Describe the business problem the integration solves and anything another user needs to know before working in it — a clear description on the Home page saves everyone from opening the integration to find out what it does.

  1. Go to Home home-icon.png, and then open the integration.
  2. Select Admin. If it isn't in the tab bar, select More > Admin.
  3. On General, change the Name or Description, and then select Save. To let Ora make changes to this integration without staging them for your approval, select Allow Ora to apply changes automatically; see Celigo Ora overview.
  4. To add documentation, select Readme > Edit readme, enter plain text in Data, check it in Preview, and then select Save.

For an integration with a few simple flows, write the documentation in the readme itself. For an integration with many complex flows, keep the documentation in separate documents and put links to them in the readme.