Export Project
Configure the ExportProject project action to send project data to external systems via a connector.
Overview
The Export Project action exports the current project to an external system using a configured connector. This is useful for integrating project workflows with ERPs, CRMs, third-party ticketing systems, or any external platform that needs to receive project data.
When this action executes, Omnium calls the specified connector's Export method with the full project object and any configured properties. The result determines whether the workflow continues or stops.
Key behaviours:
- The export is awaited — the workflow waits for the export to complete before moving to the next action
- On success, any previous
ProjectExportErroris cleared from the project - On failure with
StopOnError: true, aProjectExportErroris added to the project and the workflow is cancelled - On failure with
StopOnError: false, the result is downgraded to a warning and the workflow continues
Identifier
| Property | Value |
|---|---|
| Key | ExportProject |
| Group | Project Actions |
Configuration
Minimum Required Configuration
At minimum you must specify a connector:
All Available Options
| Property | Required | Type | Description | Example |
|---|---|---|---|---|
| name | Yes | string | Must be ExportProject | "ExportProject" |
| Connector | Yes | string | The name of the connector to use for the export | "Webhook", "AzureServiceBus" |
| StopOnError | No | boolean | Stop the workflow and flag an error on the project if the export fails | true or false (default: false) |
| Properties | No | array | Key-value pairs passed directly to the connector's export implementation | See below |
| TranslateKey | No | string | Translation key shown in the UI action log on success | "ProjectExported" |
Example Configurations
Simple webhook export — warn on failure, continue workflow:
Critical ERP export — stop workflow on failure:
Export with additional properties passed to the connector:
Export Behaviour
On Success
- Action status is set to
Success - The
ProjectExportErrorerror (if previously set) is removed from the project - The workflow continues to the next action
- The
TranslateKey(if configured) is shown in the UI action log
On Failure — StopOnError: false (default)
- Action status is set to
Warning - The workflow continues to the next action
- The error reason is recorded in the action result
On Failure — StopOnError: true
- Action status is set to
Error - A
ProjectExportErrorerror with severityErroris added to the project - The workflow is cancelled — no further actions in the current workflow run
Error Handling
| Condition | Result | Continues Workflow? |
|---|---|---|
| Export successful | Success | Yes |
Export failed (StopOnError: false) | Warning | Yes |
Export failed (StopOnError: true) | Error + ProjectExportError on project | No |
| Unhandled exception | Error | No |
Troubleshooting
Export not executing
- Confirm
"name": "ExportProject"is spelled correctly (case-sensitive) - Verify the connector name matches the connector configured in Tenant Settings
- Check the project's workflow log for error details
Export failing
- Check the project for a
ProjectExportError— theErrorReasonfield contains the message from the connector - For Webhook connectors: verify the endpoint URL is reachable and authentication is correct
- For Azure queue connectors: verify the connection string and queue/topic name are correct
Workflow stops unexpectedly
Check whether StopOnError: true is set. If the export fails with this setting, the workflow is intentionally cancelled and the project will have a ProjectExportError error attached.
Related
- Project Actions overview
- Export Order workflow step — the equivalent action for orders
