Publish or unpublish templates and integration apps

This process is the same as creating any integration in your integrator.io account, by creating flows for the business use cases that you would like to package in your integration, as demonstrated below. The flows also include any exports, imports, mappings, JavaScript hooks for business logic, and so forth that you would like to distribute with your App.

You can add settings to your integration to ask the customer for information.

You will then be able to access the selected values throughout the integration to make flow decisions at runtime.

To publish an integration app, follow the steps below:

Or, to publish a template, complete the following the steps below:

Once you save, your integration app's listing appears in the integrator.io Marketplace right away, showing your company's name as the author — but it's listed with a "Request demo" badge and isn't yet installable by customers. It becomes installable only after you provision at least one license for that customer (see Step 4 below).

The customer experience will be the same as when installing any Celigo-published template or integration app from the Marketplace.

Step 4: Provision licenses (integration apps only)

When a customer clicks Request demo on your integration app's Marketplace listing, they'll see a confirmation message, and you (the publisher) will receive an email titled "Request for Integration App license" with a direct link to that app's Licenses page.

1. Click the link in the email to open the Licenses page for your integration app.
2. Click New license.
3. Fill in the license details:
   • Email: the customer's email address
   • Expires: the license expiration date
   • Environment: Production or Sandbox
   • Options: optional JSON configuration for the license
4. Click Save.

The new license appears in the list with a status of Pending install until the customer installs the app. Once the license is active, the customer will see an Install button (instead of Request demo) when they find your listing in the Marketplace.

Note: Granting the license here does not automatically notify the customer. You'll need to manually let the customer know that access has been granted before they'll know to go install the app.

It’s a best practice to get started there but not a mandatory requirement at this time.

At this point, you would demo your application to the Celigo product team once you are ready. Once the demo is approved, you would be able to list on the Marketplace. However, this process may evolve in the future.

Naming and readme format standards for 3rd party templates and integration apps

Before you publish, name your template's or integration app's components consistently and include a complete readme. Following these conventions helps Celigo review and approve your submission faster, and helps customers understand what they're installing.

Readme file

Your readme should include:

• Overview of the template or integration app.
• Installation instructions.
• Setup and configuration instructions.
• Support contacts: your (the 3rd party's) contact for support using the template.
• Services contacts: for promoting professional services to implement the template. This can be a link to your (the publisher's) own services/contact page, or to another implementation partner you've arranged to provide that service.

Template or integration app description

Format: Sync \<Export Application Record Type in Plural, starting with UpperCase> between \<Export Assistant Name> and \<Import Assistant Name>.

Examples:

• Sync Contacts and Companies between HubSpot and NetSuite.
• Sync Employees between ADP Workforce Now and Okta.

Connections

Export connection format: \<Export Assistant Name> Connection

• Example: HubSpot Connection

Import connection format: \<Import Assistant Name> Connection

• Example: Salesforce Connection

Exports

Export name formats:

• Get \<Export Assistant Name> \<Export Application Record Type in Plural, starting with lowercase>
• Example: Get Salesforce leads
• Get \<Export Assistant Name> \<Export Application Record Type in Singular, starting with lowercase> by \<identifier>
• Example: Get Salesforce lead by ID

Export description formats:

• Delta: Get all \<Export Application Record Type in Plural, starting with lowercase> from \<Export Assistant Name> that have been modified since this flow last ran. Example: Get all leads from Salesforce that have been modified since this flow last ran.
• Single record: Get a \<Export Application Record Type in Singular, starting with lowercase> from \<Export Assistant Name> by \<identifier>. Example: Get a lead from Salesforce by ID.
• Once: Get all \<Export Application Record Type in Plural, starting with lowercase> from \<Export Assistant Name> where \<Boolean field name> is false. Example: Get all item shipments from NetSuite where "Celigo[AT]_NetSuite_Newegg_Item Shipment" field is false.
• Listener/Webhook: Get all recently created and updated \<Export Application Record Type in Plural, starting with lowercase> from \<Export Assistant Name> using a Webhook. Example: Get all recently created and updated leads from Salesforce using a Webhook.

Imports

Import name formats:

• Import \<Import Assistant Name> \<Import Application Record Type in Plural, starting with lowercase>
• Examples: Import NetSuite contacts; Import FTP files
• If the import name would otherwise be a duplicate, append the configuration type: Import \<Import Assistant Name> \<Import Application Record Type in Plural, starting with lowercase>(Import configuration type)
• Examples: Import Concur contacts(Add); Import Concur contacts(Update)

Import description format: \<Import configuration type> \<Import Application Record Type in Plural, starting with lowercase> in \<Import Assistant Name> [optional, if a lookup applies: using the \<lookup identifier> as the lookup identifier].

• Examples:
• Add or update contacts in NetSuite using the email as the lookup identifier.
• Add or ignore contacts in NetSuite using the email as the lookup identifier.
• Update contacts in NetSuite using the name as the lookup identifier.
• Add contacts to NetSuite.
• Add or update contacts in NetSuite using "Celigo[AT]_NetSuite_Newegg_ContactID" field as the lookup identifier.

If the import is to FTP: \<Import configuration type> \<Export Assistant Name> \<Export Application Record Type in Plural, starting with lowercase> to/in FTP.

• Examples: Add 3dcart customers to FTP; Update 3dcart customers in FTP.

Flows and integrations

Flow/integration name format: \<Export Assistant Name> \<Export Application Record Type in Plural, starting with lowercase> to \<Import Assistant Name> \<Import Application Record Type in Plural, starting with lowercase>

• Example: Acumatica orders to NetSuite opportunities

If it's a custom record: \<Export Assistant Name> \<Export Application Record Type in Plural, starting with lowercase> to \<Import Assistant Name> \<Custom record name in NetSuite> (custom record).

• Example: Jira projects to NetSuite Celigo Jira projects (custom record)

Flow description format: This flow syncs \<Export Assistant Name> \<Export Application Record Type in Plural, starting with lowercase> as \<Import Assistant Name> \<Import Application Record Type in Plural, starting with lowercase>. Examples:

• This flow syncs Salesforce leads as HubSpot contacts.
• This flow syncs Klaviyo exclusions as NetSuite contacts.

Integration description format: Sync \<Export Application Record Type in Plural, starting with UpperCase> between \<Export Assistant Name> and \<Import Assistant Name>. Examples:

• Sync Leads between Salesforce and HubSpot.
• Sync Contacts and Companies between HubSpot and NetSuite.