Connector

What a Connector does

A Connector is a response action. It runs one action in a system your Organization already connected under Knowledge → Applications. The Flow stores the connection and the action. It never stores a credential.

Available actions:

Each action is a read or a write. A write changes the external system.

OneDrive and Google Drive

A OneDrive or Google Drive connection belongs to one Member. The connector runs under that Member's account. For this reason:

• The action runs in the Preview and in Teammate chat. It does not run in a published widget.
• Publish refuses a Flow that contains a Drive connector. The reason names the Flow.
• Write actions need an extra scope. OneDrive needs Files.ReadWrite. Google Drive needs drive.file. Select Grant access to add it.
• With drive.file, Google Drive lets the connector change only files the connector created or that a person opened with it. Copy, share, and delete can fail on other files.
• Get file content returns text only, up to a bounded size. Binary files and Google Docs are not converted.

Add a Connector

1. Open a Flow.
2. In the Canvas, select a provider under Connector in the palette. In the Form, select Connector under Add an action and then select the provider.
3. Select a Connection. The list shows the Organization's connections for that provider.
4. Select an Action.
5. Fill in the fields. Template variables such as {{user.name}} and {{workflow.message}} are allowed where the field says so.

If the provider has no connection, connect it under Knowledge → Applications first. For Slack, the panel can open the sign-in window directly.

Salesforce cases

Create case opens a Case in the connected Salesforce org. Update case changes an existing Case.

• The fields are Subject, Description, Priority, Status, Origin, Requester email, and Requester name. Each field accepts template variables.
• Create case sets Origin to Web by default. A blank field keeps the Salesforce default.
• Requester email and Requester name go into the web email and web name fields of the Case. A Visitor who is not a Salesforce Contact can open a Case.
• Update case needs a Case id. Usually this is {{connector.case_id}} from an earlier Create case. Only the fields that you fill in change.
• The Salesforce user who connected the application must have the Create permission on Cases for Create case, and the Edit permission for Update case. The connection needs no new scope.

If Salesforce refuses the Case, for example because a required field is empty or a validation rule fails, the action fails. The Salesforce message shows in Run node and in the conversation trace. The Flow continues with its usual failure rule.

After a write, Ciele reads the Case number. If that read fails, the write still succeeds and keeps the Case id and link. The number is empty. Use Get Case records with that id and the CaseNumber field to read it later.

Fields loaded from the system

Some fields load their values from the connected system: ServiceNow tables and columns, Salesforce fields, the Salesforce Case picklists (Priority, Status, Origin), Slack channels. Select Load options to fetch them. You can still type a value.

Needs setup

A Connector node shows Needs setup when:

• The action or the connection is not selected.
• A required field is empty.
• The connection lacks a scope the action needs. Select Grant access to re-run the provider sign-in with the missing scopes added.
• The connection needs to be reconnected.

Outputs

An action writes its results to template variables for later actions in the same Flow. The names start with connector.:

{{connector.ok}} is true or false after every action. A Message action after the Connector can show these values.

What the Visitor sees

• A write that succeeds shows the Success message. The default is a short confirmation.
• A read that succeeds shows nothing. Use a Message action to show the results.
• Any failure shows the Failure message. The provider's error is never shown to the Visitor. The Editor sees it in Run node and, for an expired connection, in Alerts.

Run node

Select the node, then Run node. The console makes the real call with sample values.

• A read runs at once.
• A write asks for confirmation first, because it changes the external system.

Test connection checks that the connection's token still works.

Publish

Publish refuses a Flow whose Connector:

• names a connection that no longer exists,
• names a personal connection (OneDrive or Google Drive accounts belong to one Member),
• names a connection that lacks the action's scopes or needs to be reconnected.

The reason names the Flow. Fix the connection or the Flow, then publish again.

Expired connections

When a call fails because the provider rejected the token, the connection is marked Reauthorization required and an Integration alert is raised. Reconnect the application under Knowledge → Applications. The alert clears on reconnect.

API, CLI, and MCP

• GET /api/v1/applications/connections lists the connections without credentials.
• GET /api/v1/applications/connectors lists the catalogue.
• POST /api/v1/applications/connections/{id}/reconsent returns the scope union and the URL to open to grant it.

The same operations are ciele applications list|connectors|reconsent and the manage_integrations MCP tool actions application_list, application_connectors, application_reconsent.