Quickwork enables businesses to use pre-built Journey templates that can be embedded into their own products, portals, or systems. These are called Embedded Journeys.
An Embedded Journey is already configured in Quickwork with the required trigger, actions, and business logic. This allows end users to run automation without building a Journey from scratch or understanding the underlying workflow complexity.
The Embedded Journeys APIs are organised around two base entities:
| Entity | Purpose |
|---|---|
| Partners | Used by the partner application to manage users, connections, Embedded Journeys, and Embedded Journey instances. |
| End Users | Used by the partner’s users to configure their own Journey instances, manage connections, retrieve app details, picklists, and extended schema. |
