Importing companies from an installed extension

Rather than adding companies by hand, CloudRadial AutomationAI can build your company registry from a system that already has the list, such as your PSA. This article covers the one-click import workflow, the steps that follow it, and how to keep the registry current on a schedule. It is for workspace users with the Admin role or higher.

• Before You Start
• Creating the Import Workflow
• Reviewing and Publishing
• Deploying and Running the Import
• Reading the Import Result
• Re-Running and Resetting
• Keeping the Registry Current

Before You Start

You need an installed extension that can list companies, with its credentials already in your runner's Key Vault, and a registered runner on version 1.7.0 or later. Import writes company identities and aliases only. It never sets secret policies, so a policy you have configured is not overwritten by a re-import.

Creating the Import Workflow

Open Companies. While the registry is empty, the page offers Create import workflow. Select it, choose the installed extension to import from, and AutomationAI generates a workflow for that source, files it under an AutomationAI folder, and opens it in the Designer.

The generated workflow is deliberately small: a Start node, a single PowerShell script step, and an End node. The listing tool and its paging and required arguments are discovered when the workflow is generated and written into a CONFIG block at the top of the script, where you can read and correct them.

Reviewing and Publishing

Review the CONFIG block before you publish. If your source needs a filter, a page size, or a required argument the generator could not infer, set it there. Then publish the workflow version as you would any other; see the article on understanding workflow versions.

The script step reads from the extension using read-only tools. Mutating tools are withheld from a script step, because a script step has no approval loop, so an import can list companies but cannot change anything in the source system.

Deploying and Running the Import

Deploy the published version to a runner, then run the deployment. The Companies page deep-links each of these steps once the workflow exists, so you can follow them in order without hunting through the sidebar.

Reading the Import Result

The step's output reports what the import did:

Companies are written in batches of up to 500, and a failure on one record does not abandon the rest of the batch. If failed is above zero, open the run in History to see which records failed and why.

Re-Running and Resetting

Re-running the import is safe. A company that already exists is matched on its Company ID and left alone, so a second run reports its records as unchanged rather than creating duplicates.

To start over from an empty registry, use Manage > Delete all on the Companies page and run the import again. Deleting is permanent, so it requires typed confirmation.

Keeping the Registry Current

Attach a Routine to the import workflow to re-run it on a schedule and pick up companies added in the source system. See the article on scheduling a workflow with Routines. Because the import is idempotent, a nightly schedule adds what is new and leaves everything else untouched.

If you are still having trouble, we're here to help! Submit a ticket for assistance, and don't forget to check our status page to ensure there are no outages in your area.