Skip to content

Business Systems & ERP

Corporate Memory's workflow automation connects to the business systems your workflows run on, most commonly your ERP, alongside industry data sources relevant to your operation. Because every customer's systems and processes differ, these connections are scoped and configured per engagement rather than offered as one-size-fits-all connectors.

This page describes the integration pattern; the specifics for your organization are designed with your WorkDone implementation contact.

How these integrations work

Whatever the target system, the same principles apply:

  1. WorkDone reads working data from your systems over a secured exchange agreed with your IT team, for example scheduled file exchanges over an encrypted connection, or API access where your system provides it.
  2. Automation prepares proposed updates, enriching your data with agreed external and industry data sources where the workflow calls for it.
  3. A person in your organization reviews and approves every proposed change in the Corporate Memory portal before anything is written back. Nothing updates your systems automatically.
  4. Write-backs are confirmed and tracked. Updates sent to your systems are traced through to confirmation, and administrators can review the full history in the portal.

Human approval is structural

The review-and-approve step is not a configuration option; it is how the workflow is built. Your systems remain the system of record, and your people remain the gate.

What you provide

Worked out with your implementation contact during onboarding:

  • A connection method your IT team is comfortable with (secured file exchange, API credentials, or another agreed mechanism), using a dedicated service account with the minimum access the workflow needs.
  • An agreed data format and scope: which records, fields, and update types are in play.
  • Named reviewers: the people in your organization who will review and approve proposed updates (they'll typically hold the Automation role; see SSO & Identity).
  • Subscriptions or licenses for any third-party data sources the workflow enriches from, where applicable; data retrieved under your subscription is used only within your tenant.

Security notes

  • Connections use dedicated, narrowly scoped credentials; read-only wherever the workflow allows, write access only for the specific update path you approve.
  • Data exchanged with your systems stays inside your organization's tenant. See Security and Compliance.
  • You can suspend or revoke the connection on your side at any time; workflows pause rather than fail unsafely.

Changing or extending the integration

Workflow automation is expected to evolve: new record types, additional data sources, changed review rules. Raise changes with your implementation contact or support; scope changes follow the same review as initial onboarding.