Power Automate

Build Power Automate flows and Power Apps that create, find, and update xpntl work through a workspace-scoped custom connector.

Download: xpntl Power Automate connector v1.1.0 (Swagger JSON)

The definition uses Swagger/OpenAPI 2.0 for Power Platform custom-connector import. It targets https://api.xpntl.ai/v1 and includes 34 actions for issues, comments, projects, project lists, labels, teams, users, and API health.

Before you start

A Power Automate or Power Apps plan that supports custom connectors
An xpntl workspace and permission to create an API key
The downloaded connector definition above

1. Create an API key

Open xpntl and go to Settings → API Keys.
Select Create API Key and give it a name such as Power Automate.
Select only the scopes required by your flows.
Copy the key when it appears. xpntl shows it once.

For access to every action in the connector, select these scopes:

Resource	Scopes
Issues	`issues:read`, `issues:write`
Comments	`comments:read`, `comments:write`
Projects	`projects:read`, `projects:write`
Labels	`labels:read`, `labels:write`
Teams	`teams:read`
Users	`users:read`

2. Import the connector

In Power Automate, open Data → Custom connectors.
Select New custom connector → Import an OpenAPI file.
Choose the downloaded xpntl-power-automate.swagger.json file.
Review the imported host api.xpntl.ai and base URL /v1.
Create or update the connector.

3. Create the connection

The imported Security settings should read:

Setting	Value
Authentication type	API Key
Parameter name	`Authorization`
Parameter location	Header

When Power Platform asks for the API key, enter the complete header value:

Bearer xp_live_your_key_here

Include the word Bearer, one space, and the key. Do not add quotation marks. Power Platform's API Key authentication does not add the Bearer prefix for you.

4. Test the connector

Open the connector's Test tab.
Select the connection you created.
Run List projects or List issues.
Confirm the response contains resources from the API key's workspace.

Power Platform's test harness can display skipAuthorization: true for its own maker session. That does not disable the API-key connection. The selected connection still supplies the xpntl Authorization header.

Project keys and project IDs

A project key such as CX is a readable prefix, not the value accepted by projectId. Connector v1.1.0 loads project choices through List projects, displays the project name, and submits its internal id.

For an older flow, run List projects, find the object whose key is CX, and map its id into projectId. Do not map key.

Updating an existing connector

Download the current JSON definition from this page.
Open the custom connector's General page and upload the new file.
Save or update the connector.
Reopen the flow action so Power Automate refreshes its inputs.
Create a new connection if you changed or rotated the API key.

Troubleshooting

Problem	What to check
`401 unauthorized`	Select a connection on the Test tab and enter `Bearer xp_live_...` as the connection value. If the connector was already saved, recreate the connection so it does not reuse the old credential.
`CX is not a valid project ID`	Select the project from the dynamic list or map `List projects → projects → id`. A project key is not an ID.
Red error on a URL containing `{key}` or `{id}`	Upload connector v1.1.0 or later. It declares every path input on the individual operation for compatibility with the Power Platform designer.

Keep the connection secure

Never put a real API key in the Swagger file, a flow input, a screenshot, or source control.
Store the key only in the Power Platform connection.
Use a dedicated key for each integration and select only the scopes it needs.
Revoke the key immediately from Settings → API Keys if it is exposed.
Flow owners and connection owners should be reviewed when sharing or exporting a flow.

Self-hosted xpntl

Before importing, change the JSON definition's top-level host from api.xpntl.ai to your API hostname. Keep basePath as /v1. Use HTTPS outside local development.