---
title: Microsoft Power Platform
description: The Coevera connector for Power Automate, Power Apps, Copilot Studio and Logic Apps covers five record types by ID and has no triggers.
canonical: https://developers.coevera.com/integrations/power-platform/
section: integrations
publisher: Coevera
---

# Microsoft Power Platform

**Answer:** Microsoft lists the Coevera connector as Pipeliner CRM (Preview). It gets, creates, updates and deletes accounts, contacts, leads, opportunities and tasks by ID, and has no triggers. It signs in with an API application's user name and password, and every action also asks for the service URL and space ID. Microsoft limits it to 100 calls per connection per minute.

This page describes the connector as Microsoft documents it in its
[connector reference](https://learn.microsoft.com/en-us/connectors/pipelinercrm/). In the Microsoft products, search
for **Pipeliner CRM (Preview)**: the connector carries the company's former name.

## Where it is available

| Product        | Class    |
| -------------- | -------- |
| Power Automate | Premium  |
| Power Apps     | Premium  |
| Copilot Studio | Premium  |
| Logic Apps     | Standard |

Microsoft does not offer it in its US government, China or US Department of Defense clouds.

## Connect

1. In Coevera, create an API application for the connector and give it the
   [permissions](/get-started/permissions-and-scopes/) your flows need. The
   [quickstart](/get-started/quickstart/#get-api-credentials) shows where to create it.
2. In Power Automate, Power Apps, Copilot Studio or Logic Apps, add the connector and create a
   connection with the application's **user name** and **password**.
3. In each action, enter the **Service URL** (it starts with `https://`) and the **Space ID**.
   Both are shown under **Show Access** for the application.

The connection cannot be shared. When you share a Power App that uses it, each user is asked to
create their own connection.

## Actions

Twenty actions, four for each of five record types:

| Record type | Get | Create | Update | Delete |
| ----------- | --- | ------ | ------ | ------ |
| Account     | Yes | Yes    | Yes    | Yes    |
| Contact     | Yes | Yes    | Yes    | Yes    |
| Lead        | Yes | Yes    | Yes    | Yes    |
| Opportunity | Yes | Yes    | Yes    | Yes    |
| Task        | Yes | Yes    | Yes    | Yes    |

**Get** returns one record by its ID, and **Delete** removes one record by its ID. **Update**
modifies one or more records by ID. There is no action that lists or searches records.

## No triggers

The connector cannot start a flow when something changes in Coevera. For event-driven flows,
either:

- register an [API webhook](/webhooks/overview/) that posts to a flow that starts on an HTTP
  request, or
- use [Zapier](/integrations/zapier/), whose Coevera app has triggers for new and updated records.

## Limits

- **100 calls per connection per 60 seconds.** This is Microsoft's throttling of the connector,
  not a Coevera limit.
- Coevera's own limit is the number of API calls a space can make each month, which depends on
  its plan; see [coevera.com/crm/pricing](https://www.coevera.com/crm/pricing/).

## Where it stops

Only five record types: no appointments, products, quotes, projects, documents or custom
entities. No business actions such as qualifying a lead or moving an opportunity, and no list or
search. For those, call the API, from a flow's HTTP action with an API application's
credentials or from your own code. See [Integration platforms](/integrations/overview/) for how
the options compare.