C TWO (Preview)

This connector is available in the following products and regions:

Service	Class	Regions
Copilot Studio	Premium	All Power Automate regions except the following:      -   US Government (GCC)      -   US Government (GCC High)      -   China Cloud operated by 21Vianet      -   US Department of Defense (DoD)
Logic Apps	Standard	All Logic Apps regions except the following:      -   Azure Government regions      -   Azure China regions      -   US Department of Defense (DoD)
Power Apps	Premium	All Power Apps regions except the following:      -   US Government (GCC)      -   US Government (GCC High)      -   China Cloud operated by 21Vianet      -   US Department of Defense (DoD)
Power Automate	Premium	All Power Automate regions except the following:      -   US Government (GCC)      -   US Government (GCC High)      -   China Cloud operated by 21Vianet      -   US Department of Defense (DoD)

Contact
Name	C TWO Support
URL	https://ctwo.com/
Email	customersuccess@ctwo.com

Connector Metadata
Publisher	C TWO
Website	https://ctwo.com/
Privacy policy	https://ctwo.com/privacy-policy/
Categories	Business Intelligence;AI

C TWO

C TWO is an Agentic Management Platform that orchestrates automation workflows, manages human‑robot interactions, and processes work items through universal queues. This connector lets Power Automate, Power Apps, Azure Logic Apps, and Copilot Studio trigger and be triggered by C TWO sessions, manage session lifecycle, create and process Universal Queue items, and enable human‑in‑the‑loop interactions with digital workers.

C TWO sits above your automation estate as a single orchestration, governance, and monitoring layer: whatever creates or executes the work, C TWO adds SLA tracking, retries and self‑healing, live session telemetry, and a full audit trail.

Prerequisites

Before creating a connection you will need:

1. An active C TWO tenant — either C TWO Cloud (hosted) or an on‑premises C TWO server reachable over HTTPS.
2. A Service Account token or Personal Access Token issued by your C TWO administrator (see Obtaining credentials).
3. If C TWO is hosted on‑premises, the server must be reachable from Power Platform over HTTPS (firewall allowing Microsoft's Power Automate outbound IP ranges — Azure Service Tags AzureConnectors.<region> and PowerPlatformPlex for your Power Platform Geo).
4. A Power Platform environment with Custom Connector permissions and a license tier that supports custom connectors (Power Automate Premium or equivalent).

Creating a connection

When you create a connection you provide three values, all from your own C TWO environment:

1. C TWO Host — your C TWO server hostname only (no scheme, no trailing slash), e.g. connect24.ctwo.cloud, or an on‑premises host with optional port such as ctwo.contoso.com:8443.
2. C TWO Base URL — the base path of your C TWO API including your division, starting with a slash and with no trailing slash, e.g. /DEFAULT/CTWO.Server/api.
3. API Key — your token, entered as Bearer <your-token>. A Service Account token is recommended; a Personal Access Token also works.

Together, Host and Base URL route the connector to your own C TWO server (https://{Host}{Base URL}/…), so each customer connects to their own environment — C TWO Cloud or on‑premises.

Obtaining credentials

Authentication uses an API key sent as a Bearer token in the Authorization header.

Service Account token (recommended for production)

1. Sign in to your C TWO instance.
2. Go to Apps and Connections → Microsoft Power Automate → Create service account.
3. Copy the generated token immediately — it is shown only once.

Personal Access Token (development/testing)

1. Open your user profile in C TWO.
2. Go to the API Tokens tab and generate a new token.
3. Copy it immediately — it is shown only once and is invalidated if the user account is disabled.

Treat both token types as secrets — store them only in the Power Platform connection credential, never in flow variables or client‑side code.

Supported operations

• Triggers — Start a flow when C TWO dispatches a session, with or without an enforced timeout.
• Session management — Report completion/failure, write typed session logs, adjust the session timeout, and check for a graceful stop request.
• Universal Queue — Create, list, lock, unlock, retry, and defer queue items; update item data and add item‑level logs; add/remove tags; retrieve attachments; create custom item states; list queues.
• Human‑in‑the‑loop — Create, assign, unassign, and complete structured human‑assistance forms, and retrieve/query them.

Internal helper operations populate dynamic dropdowns (task and user pickers) and are not called directly.

Known issues and limitations

• Correct Host and Base URL required. Both are entered at connection time and route the connector to your C TWO server. Incorrect or unreachable values result in connection or request failures.
• API Key format. The API Key field expects the literal string Bearer <token> — omitting the Bearer prefix results in 401 Unauthorized.
• Supplying JSON item data. Item‑data fields (Create Queue Item, Set Queue Item Data) are JSON objects. In a flow, supply literal JSON with the json('…') expression so it is sent as an object rather than a string.
• Polling trigger latency. Triggers poll rather than push, so there is a small delay (bounded by the trigger recurrence) between a session being dispatched in C TWO and the flow starting.
• Form field types. Some identifier fields returned by the form operations may be an integer, a string, or null depending on the form's state.

Common errors and remedies

Error	Likely cause	Remedy
401 Unauthorized	API Key missing the Bearer prefix, expired, or revoked	Re‑enter the credential as Bearer <token>; generate a new Service Account token if revoked
400 Bad request on Create Queue Item	Missing a required field (reference, queueItemState, itemKey)	Populate all three required fields
Trigger never fires	Wrong task selected, or the C TWO task is not exposed to Power Automate	Confirm the task appears in the Task ID dropdown and is configured as an exposed flow in C TWO
Item data stored as an escaped string	JSON supplied as text instead of an object	Use the json('…') expression (flows) or Raw Body (connector test) so it is sent as an object

FAQ

Can I use this connector from Power Apps, Azure Logic Apps, and Copilot Studio, not just Power Automate? Yes. The triggers are Power Automate–specific, but every action can be called from any of these platforms once a connection is created.

Does this connector manage licensing? No. C TWO orchestrates and governs execution; customers are responsible for their own Microsoft licensing.

Where can I get help? Contact C TWO Customer Success at customersuccess@ctwo.com.

Creating a connection

The connector supports the following authentication types:

Default	Parameters for creating connection.	All regions	Not shareable

Default

Applicable: All regions

Parameters for creating connection.

This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.

Name	Type	Description	Required
C TWO Host	string	Your C TWO server hostname only — no scheme, no trailing slash. For example connect24.ctwo.cloud, or an on-premises host with optional port such as ctwo.contoso.com:8443.	True
C TWO Base URL	string	The base path of your C TWO API including your division. Start with a slash, no trailing slash. For example /DEFAULT/CTWO.Server/api.	True
API Key	securestring	Your C TWO API token, entered as: Bearer <your-token>. A Service Account token is recommended; a Personal Access Token also works.	True

Actions

Add Log to Queue Item	Adds a log message to a queue item for audit trail and traceability. Use this action to record processing steps, warnings, or errors against a specific work item.
Add Log to Session	Writes a log entry to a C TWO session. Use this action to track progress, record decisions, or log diagnostic information during flow execution. Logs are visible in the C TWO platform for auditing and troubleshooting.
Add Tags to Queue Item	Adds one or more tags to a queue item for categorization and filtering. Tags help organize and search for work items across queues.
Assign Form	Assigns a robot interaction form to a specific user, making them responsible for reviewing and completing the human-in-the-loop request.
Complete Form	Marks a robot interaction form as completed, signaling that the human user has provided the requested input and the digital worker can resume processing.
Create Form	Creates a new robot interaction form that allows a digital worker to request human assistance. The form is presented to assigned users in the C TWO platform, enabling human-in-the-loop scenarios where human expertise is needed to handle exceptions or complex decisions.
Create Queue Item	Creates a new work item in a specified universal queue. Use this action to add items for processing by digital workers, including data payloads, tags, and optional file attachments.
Create Queue Item State	Creates a new custom state within a specific queue. Custom states allow you to define workflow stages beyond the default states (Pending, Completed, Referred), tailoring the queue to your business process.
Defer Queue Item	Defers a queue item so it will not be processed until the specified date/time. Use this action when an item cannot be processed now but should be retried later.
Get Form By Id	Retrieves a specific robot interaction form by its unique identifier. Use this action to fetch the details, fields, and current status of a human-in-the-loop form that was created by a digital worker.
Get Forms	Retrieves a list of robot interaction forms with optional filtering. Use this action to query pending human-in-the-loop requests, check their status, or find forms assigned to specific users.
Get Queue Item Attachment	Retrieves a specific file attachment from a queue item as base64-encoded data. Use this action to download files that were attached to work items during creation or processing.
Get Queue Items	Retrieves queue items based on specified filter criteria such as state, tags, dates, and queue names. Use this action to search for and monitor work items across your universal queues.
Get Queues	Retrieves universal queues based on filter criteria. Use this action to list available queues, check their configuration, or look up queue details. This operation also powers dynamic dropdowns in other actions.
Lock Queue Item	Locks a queue item to prevent other workers from processing it concurrently. Use this action before processing a work item to ensure exclusive access.
Remove Tags from Queue Item	Removes one or more tags from a queue item. Use this action to update the categorization of work items during processing.
Retry Queue Item	Retry a specific queue item, setting its data back to its original value and creating a new Attempt.
Set Flow Execution State to Completed	Marks a C TWO session as completed, signaling that the flow has finished its work successfully. Place this action at the end of your flow to report back to C TWO that the automation completed without errors.
Set Flow Execution State to Failed	Marks a C TWO session as failed, signaling that an error occurred during flow execution. Use this action in error-handling scopes to report failures back to C TWO with details about what went wrong.
Set Queue Item Data	Updates the data content of a queue item. Use this action to modify the payload of a work item during processing, for example to store intermediate results.
Set Queue Item State	Changes the state of a queue item (e.g., from Pending to Completed, or to a custom state). Use this action to advance items through your workflow pipeline.
Set Session Timeout	Updates the timeout value for an active C TWO session. Use this action to extend or reduce the allowed execution time for a running session when the original timeout needs adjustment.
Should Session Stop	Checks whether C TWO has requested a graceful (soft) stop for the given session. Use this action inside loops to periodically check if the session should terminate early, allowing the flow to clean up resources before stopping.
Unassign Form	Removes the current user assignment from a robot interaction form, making it available for other users to claim.
Unlock Queue Item	Unlocks a previously locked queue item and returns it to its available state. Use this action when processing is interrupted and the item should be released for other workers.

Add Log to Queue Item

Add Log to Session

Add Tags to Queue Item

Assign Form

Complete Form

Create Form

Create Queue Item

Create Queue Item State

Defer Queue Item

Get Form By Id

Get Forms

Get Queue Item Attachment

Get Queue Items

Get Queues

Lock Queue Item

Remove Tags from Queue Item

Retry Queue Item

Set Flow Execution State to Completed

Set Flow Execution State to Failed

Set Queue Item Data

Set Queue Item State

Set Session Timeout

Should Session Stop

Unassign Form

Unlock Queue Item

Triggers

Start Flow from Session Request with Timeout	Polls for new C TWO sessions and triggers the flow with a timeout constraint. Use this trigger when the automation must complete within a specific time window. If the session exceeds the timeout, C TWO will handle it according to its timeout policy.
Start Flow from Session Request without Timeout	Polls for new C TWO sessions and triggers the flow when a session is created for the selected task. Use this trigger when the automation does not require a timeout constraint. The flow receives session details including input values passed from C TWO.

Start Flow from Session Request with Timeout

Start Flow from Session Request without Timeout

Definitions

string

object