Integration Node

An integration node ("type": "integration") calls out to an external system. It has a single handler class, integration, and its process is an action reference — it names the action to run rather than carrying its configuration inline. Use this page when building nodes for Create a Workflow or Update a Workflow.

Process Fields

string

required

The action to run — what this step does on the external system, such as Send Message or Create Row.

string

What the action does.

object

required

The integration the action belongs to.

Show Integration object

string

required

Integration display name

string

What the integration connects to

string

Integration icon

object

required

The vendor or system behind the integration.

Show Provider object

string

required

Provider display name — for example Slack, Google

string

What the provider is

string

Provider icon

The nesting mirrors how integrations are organised in Opus: a provider is the vendor, an integration is a connection to it, and an action is one operation on that integration.

Example

integration node

{
  "id": "{NODE_ID}",
  "name": "Post To Slack",
  "type": "integration",
  "handler_class": "integration",
  "process": {
    "name": "Send Message",
    "description": "Post a message to a channel",
    "integration": {
      "name": "Slack",
      "description": "Team messaging",
      "provider": {
        "name": "Slack",
        "description": "Slack Technologies"
      }
    }
  }
}

Credentials are never part of the node. They are attached to the integration itself — see Create a Credential.

Integrations API

Create providers, integrations and credentials through the API

Integrations Marketplace

Pre-built connectors available in Opus

Get Started

Workflows

Cases

Files

Business Process Discovery

Integrations

Agents

Deprecated

Process Fields

Example

Integrations API

Integrations Marketplace

​Process Fields

​Example

​Related

Integrations API

Integrations Marketplace

Process Fields

Example

Related