Auth-only dialog experience
Notes on Auth dialog URL and regionCopy
When initiating the Auth dialog for your End Users, you will need to compose the Auth dialog URL as such
This URL will vary depending on your region.
If you are in the EU region, the URL would be:
If you are in the APAC region, the URL would be:
Register a userCopy
Log existing user inCopy
List available integrationsCopy
User configures integrationCopy
You could have one connect button which creates the solutions instance and one authorize button for each service in the integration as shown above. Follow these steps to present this experience for end users:
Create solution instanceCopy
Initialize auth only dialogCopy
Note that these steps would be repeated for each service auth that the end user provides:
Enable the Solution InstanceCopy
You can now return to the Users section of the UI and see that the Solution Instance for that End User is there, but currently disabled (this is to allow you to make any checks or changes before an Instance is activated):
Please not the warning below when enabling instances through the API:
Run and testCopy
Trigger a run of the Workflow InstanceCopy
Now you can paste the triggerUrl into your browser address bar and hit 'enter' to trigger a run of the Workflow Instance.
Debugging the Solution InstanceCopy
Return to the Users page on the UI and click on your end user. You will now see that the Solution Instance is enabled and you can click on 'Debug Workflows' on the solution instance card as shown below:
This will open a modal of all the linked workflows of this solution instance. You can the debug the workflow that you want.
This will open a read-only version of the Workflow in a new tab:
List an End User's Solution InstancesCopy
User edits integrationCopy
Follow these steps to present this experience for end users:
Note that the steps above would be repeated for each service auth that the end user provides.
Note on updating Solution InstancesCopy
When you (not end user) publish a new version of a Solution, there are two types of updates that would happen to all Solution Instances linked to this Solution:
A 'lazy' update (no new config or auths are required)
A 'breaking changes' update (i.e. requires new auth and/or config data) whereby you will have to notify End Users to edit their integrations as above
For more details, please see our guide to Updating Solutions and Instances.
User deletes integrationCopy
Delete solution instanceCopy
Users may want to delete the instance they no longer wish to use and you can achieve it by following the steps below: