Ellipse Gradient for Header

Microsoft Power Automate Integration Guide

Microsoft Power Automate integrates enterprise processes through cloud flows, HTTP endpoints, REST APIs, connector triggers, files, databases, and Microsoft data services.

Microsoft Power Automate integration options at a glance

Microsoft Power Automate supports REST-based management and platform APIs, HTTP-triggered flows, connector-specific triggers, webhook-style callbacks for selected connectors, and asynchronous processing through arrays, loops, concurrency, and child flows. It also connects to files, attachments, databases, Dataverse, and other Microsoft or third-party services through individual connectors. Microsoft Entra ID and OAuth 2.0 secure platform APIs, while connectors may use their own authentication schemes. Martini can call HTTP-triggered flows, consume Power Platform APIs, expose REST APIs for Power Automate, and orchestrate validation, mapping, retries, persistence, and downstream integration logic.

Integration pointSupported by Microsoft Power Automate?Common use casesHow Martini supports it
REST APIsYesMicrosoft Power Automate and Power Platform REST APIs support applicable administration and platform operations for environments, flows, runs, connections, and related resources. Flows can also call external REST APIs through HTTP actions or custom connectors.Martini can consume REST APIs, authenticate requests, map responses, paginate through results, and expose reusable REST APIs for Power Automate to call.
HTTP request and response endpointsYesPower Automate can start flows with an HTTP request and may return a synchronous HTTP response when the flow design and execution model support it.Martini can call an HTTP-triggered flow or expose an API that Power Automate invokes, with workflow-based validation, transformation, routing, and response handling.
Webhooks and outbound callbacksLimitedSelected connectors and custom connector scenarios support webhook-style triggers or callbacks. Coverage, subscription lifecycle, payloads, and retries depend on the connector.Martini can receive webhook requests, validate signatures or tokens where applicable, process the payload, and call callback endpoints or downstream APIs.
Bulk, asynchronous, and batch processingLimitedPower Automate supports asynchronous execution, arrays, loops, concurrency, child flows, and connector-specific batch operations, but has no universal bulk API for all connectors.Martini can split or aggregate batches, control concurrency, persist checkpoints, apply bounded retries, and invoke connector or HTTP endpoints according to their limits.
File and attachment APIsLimitedFile and attachment actions are supplied by individual connectors such as SharePoint, OneDrive for Business, and Outlook rather than by one universal Power Automate file API.Martini can exchange file payloads through HTTP flows, transform file metadata or content, and interact with storage APIs or file-capable endpoints.
Database and business-data accessLimitedPower Automate accesses SQL Server, Dataverse, Azure services, and other data sources through connectors. Operations and limits depend on the connector or service API.Martini can call relevant APIs, connect to supported databases, map data models, and coordinate writes with transaction, retry, and error-handling logic where appropriate.
AuthenticationYesPlatform APIs use Microsoft Entra ID and OAuth 2.0. Individual connectors may use OAuth, API keys, Basic Authentication, service accounts, custom connector schemes, or gateway credentials.Martini stores tenant identifiers, client credentials, tokens, environment values, and endpoint settings in secure configuration rather than workflow logic.
GraphQL APIsNot confirmedNo official general-purpose Power Automate GraphQL API was identified. GraphQL may be reachable through generic HTTP capabilities, but it is not a documented native Power Automate API mechanism.Martini can consume GraphQL APIs when an external GraphQL endpoint is available, but this should not be represented as a native Power Automate GraphQL capability.

How Microsoft Power Automate exposes data and business events

Microsoft Power Automate REST APIs

Microsoft provides REST-based management and platform APIs for applicable Power Automate and Power Platform administration, including environments, flows, flow runs, connections, and related resources. Availability and permissions vary by API and tenant context.

Martini implementation pattern

Martini implementation pattern: a scheduled or on-demand Martini workflow authenticates with Microsoft Entra ID and OAuth 2.0, calls the relevant API, follows pagination or continuation links, maps the response to an internal model, and stores checkpoints or operational results.

Implementation sequence

Authenticate with Microsoft Entra ID and OAuth 2.0
Call the applicable Power Automate or Power Platform REST endpoint
Follow continuation links or next-page tokens
Map resources and statuses to the internal model
Persist checkpoints and raise alerts for relevant failures

HTTP-triggered flows

Power Automate can expose a flow through an HTTP request trigger and may return a synchronous HTTP response when supported by the flow's execution model. The endpoint URL and authentication requirements must be protected as credentials.

Martini implementation pattern

Martini implementation pattern: Martini receives a business event, validates and transforms it, calls the HTTP-triggered flow with the required headers and payload, and records the response, correlation identifier, or accepted status for asynchronous follow-up.

Implementation sequence

Receive the source event in a Martini workflow
Validate the business payload and required fields
Transform the payload to the Power Automate contract
Call the protected HTTP-triggered flow
Persist the response and correlation identifier
Poll or receive a callback when the process is asynchronous

Connector triggers and callbacks

Power Automate supports event-driven connector triggers, including webhook-style subscriptions or callbacks for selected connectors. Other connectors use polling, recurrence, or service-specific event mechanisms, so coverage is connector-specific.

Martini implementation pattern

Martini implementation pattern: Martini receives a supported event or callback, verifies the request according to the connector contract, applies deduplication and business rules, and invokes downstream APIs or returns a controlled acknowledgement.

Implementation sequence

Receive the connector event or callback
Validate authentication, signature, and payload structure
Extract the event or business identifier
Check for duplicate processing
Map and route the event to downstream systems
Return an acknowledgement or record a durable failure

Files and attachments

Power Automate processes files and attachments through services and connectors such as SharePoint, OneDrive for Business, and Outlook. File capabilities, limits, encoding, and retention depend on the selected connector.

Martini implementation pattern

Martini implementation pattern: Martini accepts a file payload or metadata from an HTTP flow or storage service, validates size and content requirements, transforms metadata or content as needed, and writes the result to the target endpoint.

Implementation sequence

Receive file content or storage metadata
Validate file type, size, and required metadata
Decode or transform the content when required
Write the file or attachment to the target service
Persist identifiers and processing status
Route failures to retry or exception handling

Asynchronous and batch processing

Power Automate supports asynchronous execution, arrays, loops, concurrency, child flows, and connector-specific batch operations. There is no universal bulk API across all connectors, and service limits apply.

Martini implementation pattern

Martini implementation pattern: Martini partitions input into bounded batches, calls the flow or target API with controlled concurrency, tracks each item or batch, and retries transient failures without replaying successful work.

Implementation sequence

Receive or retrieve the source collection
Partition items into bounded batches
Apply concurrency and rate controls
Call the flow or target endpoint
Record item and batch outcomes
Retry transient failures and isolate persistent exceptions

Common Microsoft Power Automate integration patterns

Pattern 1: Start a Power Automate approval process

When to use this pattern

Use this pattern when an enterprise application produces an event that should initiate an approval, Teams notification, Outlook task, or SharePoint document process. Martini provides a governed boundary before the event enters Power Automate.

Integration direction
Enterprise application
Martini
Microsoft Power Automate
Microsoft Teams or SharePoint
Example Mapping
Microsoft Power Automate FieldCanonical FieldTarget Field
eventIdcorrelationIdRequest identifier
requesterinitiatorRequester email
amountapprovalAmountApproval amount
documentUrlsourceDocumentUrlDocument link
Martini implementation pattern

A Martini workflow receives the source event, validates required fields, enriches it with enterprise context, and maps it to the HTTP-triggered flow contract. It calls Power Automate, persists the returned tracking identifier, and uses bounded retries and idempotency checks to prevent duplicate approvals.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • error handling

Pattern 2: Govern Power Automate calls through a Martini API

When to use this pattern

Use this pattern when multiple Power Automate flows need shared validation, canonical mapping, enrichment, routing, or access to several downstream systems. It avoids duplicating complex logic in individual flows.

Integration direction
Microsoft Power Automate
Martini
Enterprise applications
Example Mapping
Microsoft Power Automate FieldCanonical FieldTarget Field
sourceRecordIdbusinessKeyTarget external ID
sourceTypeeventTypeRouting rule
payloadcanonicalPayloadTarget request body
requestedAteventTimestampAudit timestamp
Martini implementation pattern

Power Automate invokes a Martini REST API through an HTTP action or custom connector. Martini authenticates and validates the request, transforms it into canonical form, applies routing and business rules, calls one or more target APIs, and returns a controlled response with correlation details and failure classification.

Martini capabilities used
  • APIs
  • workflow orchestration
  • data mapping
  • business rules
  • error handling

Pattern 3: Monitor Power Automate flow runs

When to use this pattern

Use this pattern when operations teams need an inventory of flows, run statuses, failed executions, or inactive resources across Power Platform environments. The exact scope depends on tenant permissions and API availability.

Integration direction
Microsoft Power Automate REST APIs
Martini
Operations catalog or alerting system
Example Mapping
Microsoft Power Automate FieldCanonical FieldTarget Field
environmentIdplatformEnvironmentIdEnvironment key
flowIdworkflowIdFlow identifier
statusexecutionStatusOperational status
errorfailureDetailIncident description
Martini implementation pattern

A scheduled Martini workflow authenticates with Microsoft Entra ID, retrieves paginated flow or run data, normalizes statuses, detects new failures using checkpoints, and sends alerts or updates an operational catalog. Transient API failures use backoff, while permission failures are retained as actionable exceptions.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination handling
  • data mapping
  • monitoring
  • error handling

Pattern 4: Coordinate Microsoft 365 business processes

When to use this pattern

Use this pattern when Power Automate performs Microsoft 365 actions while Martini provides enterprise integration, canonical data, and callback handling. It is useful for processes spanning a source application, Teams, SharePoint, Outlook, and downstream systems.

Integration direction
Source application
Martini
Microsoft Power Automate
Microsoft Teams or SharePoint
Example Mapping
Microsoft Power Automate FieldCanonical FieldTarget Field
businessEventIdcorrelationIdFlow correlation ID
customerNamepartyNameMessage or list title
approvalStatusprocessStatusFlow result status
resultIdexternalReferenceDownstream item ID
Martini implementation pattern

Martini receives and enriches the source event, invokes the Power Automate HTTP trigger, and stores the accepted response. Power Automate performs Microsoft 365 actions and can call a Martini API with resulting identifiers and status; Martini then applies idempotency, updates the source system, and routes failures for retry or review.

Martini capabilities used
  • workflows
  • REST APIs
  • data mapping
  • asynchronous orchestration
  • business rules
  • error handling

Applications commonly integrated with Microsoft Power Automate

Power Automate connects to Microsoft services and third-party applications through connectors, HTTP actions, custom connectors, and service-specific APIs. Martini can participate at the API boundary to centralize transformation, validation, routing, and operational controls.

Application Scenario Direction Martini Pattern
Microsoft Teams Send notifications, collaboration updates, approvals, and adaptive-card messages in response to enterprise events. Enterprise systems → Martini → Microsoft Power Automate → Microsoft Teams Martini receives and validates the source event, maps it to an HTTP-triggered flow contract, and stores the returned correlation or tracking identifier. Power Automate performs the Teams action and can call Martini back with completion status.
SharePoint Create or update list items, manage documents, and coordinate document approval processes. Enterprise systems → Martini → Microsoft Power Automate → SharePoint A Martini workflow canonicalizes the business payload and invokes a Power Automate flow. The flow handles SharePoint-specific actions, while Martini records identifiers, status, and errors for cross-system traceability.
Outlook Send email, process supported mailbox events, create calendar items, and coordinate notifications or approvals. Enterprise systems → Martini → Microsoft Power Automate → Outlook Martini applies recipient, template, and business-rule validation before calling an HTTP-triggered flow. Power Automate performs Outlook actions and returns an accepted or completed response according to the process design.
Microsoft Dynamics 365 Coordinate customer engagement processes and synchronize business events with Microsoft services. Microsoft Dynamics 365 → Microsoft Power Automate → Martini → Enterprise systems Power Automate triggers or orchestrates the business event, then calls a Martini API for canonical mapping, enrichment, routing, and downstream writes. Martini applies idempotency and centralized error handling before returning the result.
Salesforce Trigger notifications, approvals, or synchronization processes when Salesforce data changes. Salesforce → Microsoft Power Automate → Martini → Enterprise systems Power Automate receives a connector event or performs a connector operation and invokes Martini for reusable transformation and multi-system orchestration. Martini returns a controlled response and records correlation details.
ServiceNow Create or update incidents, requests, and operational tickets from business or integration events. ServiceNow → Microsoft Power Automate → Martini → Enterprise systems Power Automate coordinates the ServiceNow action and calls a Martini REST API where complex validation, enrichment, routing, or persistence is required. Martini can also consume ServiceNow APIs directly for governed synchronization.
SAP S/4HANA Coordinate approvals and business processes involving SAP data and Microsoft services. SAP S/4HANA → Microsoft Power Automate → Martini → Enterprise systems Power Automate handles connector-specific process steps, while Martini provides a stable API boundary for canonical SAP-related payloads, business rules, retries, and downstream orchestration.
Jira Create or update issues and notify development or service teams based on business events. Jira → Microsoft Power Automate → Martini → Enterprise systems A Power Automate connector event or HTTP request starts the process. Martini maps the event to an internal issue model, validates required fields, routes the request, and returns an idempotent result to the flow.

How to build a Microsoft Power Automate integration in Martini

Objective

Establish the Power Platform endpoint, tenant, environment, flow, and authentication configuration without embedding secrets or environment-specific values in workflow logic.

Instructions in Martini

  • Identify whether the integration uses a Power Automate HTTP trigger, a Power Platform REST API, or a Martini API.
  • Configure Microsoft Entra ID, OAuth 2.0, tenant, environment, and endpoint values as secure environment configuration.
  • Confirm required environment permissions, API permissions, connector access, and licensing.

Objective

Select the event, HTTP request, scheduled workflow, connector trigger, or callback that starts the integration and define its delivery contract.

Instructions in Martini

  • Choose a source event or schedule appropriate to the business process.
  • Document whether the flow is synchronous, asynchronous, polling-based, or callback-based.
  • Define correlation identifiers, idempotency keys, acknowledgement behavior, and retry ownership.

Objective

Obtain the Power Automate request, webhook-style event, flow metadata, flow run, file, or downstream business payload required by the process.

Instructions in Martini

  • Receive requests through a Martini API or consume the relevant Power Platform REST endpoint.
  • Handle pagination and continuation links for collection responses.
  • Validate authentication, content type, payload shape, and required identifiers.

Objective

Implement the end-to-end Martini workflow that calls Power Automate or downstream systems and coordinates synchronous and asynchronous work.

Instructions in Martini

  • Call the protected HTTP-triggered flow or platform API.
  • Persist correlation IDs, flow IDs, run IDs, and checkpoints where applicable.
  • Use branching and controlled concurrency for multi-step or batch processes.

Objective

Translate between Power Automate payloads, canonical enterprise models, and target application contracts while preserving traceability.

Instructions in Martini

  • Map request and response fields to a canonical model.
  • Transform JSON, file metadata, arrays, and status values as required.
  • Preserve source identifiers and external references for reconciliation.

Objective

Enforce validation, routing, authorization, idempotency, and business policies before committing downstream actions.

Instructions in Martini

  • Validate required fields, supported statuses, and business constraints.
  • Apply duplicate detection using event IDs, business keys, or source versions.
  • Route invalid or ambiguous requests to durable exception handling.

Common Microsoft Power Automate data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
Cloud flowsAutomated, instant, and scheduled workflows containing triggers and actions.Martini, Microsoft Teams, SharePoint, Outlook, Dynamics 365, Salesforce, ServiceNowMartini can invoke an HTTP-triggered flow, inspect applicable flow metadata through platform APIs, and persist flow identifiers and correlation data.
TriggersEvents, HTTP requests, connector notifications, or recurrence schedules that start a flow.Martini APIs, enterprise applications, Microsoft 365 services, connector-backed applicationsMartini can send requests to HTTP triggers, receive webhook-style requests where supported, validate payloads, and route events through workflows.
ActionsAPI calls, approvals, notifications, transformations, file operations, and downstream business operations within a flow.Microsoft Teams, SharePoint, Outlook, Dataverse, SQL Server, third-party applicationsMartini maps inputs and outputs around the flow boundary and can centralize operations that are better reused across multiple flows.
Flow runsIndividual executions with status, inputs, outputs, errors, and timing information.Operational monitoring, internal catalogs, alerting systems, ITSM platformsA scheduled Martini workflow can retrieve applicable run information through management APIs, follow pagination, correlate failures, and raise operational alerts.
EnvironmentsPower Platform administrative boundaries containing flows, connections, solutions, and related resources.Martini, Power Platform administration, internal service catalogsMartini can synchronize selected environment metadata while keeping environment IDs and administrative credentials in secure configuration.
Connections and connection referencesAuthenticated connector connections and solution-aware references used by flow actions and deployments.Power Platform environments, solutions, Microsoft and third-party connectorsMartini treats connector credentials as Power Automate-managed resources and integrates through flow endpoints or platform APIs rather than assuming direct access to connection secrets.

Authentication and security considerations

Microsoft Entra ID and OAuth 2.0

Power Automate and Power Platform APIs use Microsoft Entra ID and OAuth 2.0, with access further controlled by tenant identity, environment permissions, API permissions, roles, and resource-specific authorization.

Connector and trigger security

Connectors may use OAuth 2.0, API keys, Basic Authentication, service accounts, custom connector schemes, or gateway credentials. HTTP trigger URLs and callback endpoints should be treated as credentials and protected with HTTPS, appropriate authentication, request validation, and rotation procedures.

Martini configuration

  • Store tenant IDs, client credentials, tokens, environment IDs, flow IDs, and trigger URLs in secure configuration.
  • Do not assume Martini can reuse credentials held inside Power Automate connector connections.
  • Validate payloads, signatures, tokens, and authorization claims before processing requests.
  • Account for conditional access, consent, data loss prevention policies, and environment-level permissions.

Operational considerations for Microsoft Power Automate integrations

Throttling and limits

Power Automate, Microsoft Graph where relevant, individual connectors, and downstream systems can impose different throttling and service-protection limits. Use bounded concurrency, rate-aware batching, and exponential backoff.

Pagination and asynchronous execution

Management and platform APIs may return paginated results. Follow continuation links or next-page tokens. Define whether each process returns a completed result, an accepted status with tracking ID, a callback, or a result that must be polled.

Idempotency and retries

Use event IDs, business keys, source versions, correlation identifiers, and idempotent upserts to prevent duplicate actions when callers or flows retry requests.

Environment and schema changes

Keep environment IDs, flow IDs, connection references, and trigger URLs outside deployment-specific logic. Validate required fields defensively and tolerate additive schema changes where appropriate.

Testing and observability

Capture Martini correlation IDs, request identifiers, response statuses, flow IDs, and run IDs. Test connector permissions, throttling, pagination, failure paths, callback behavior, and synchronous versus asynchronous execution across development, test, and production environments.

Why use Martini instead of scripts or point-to-point integrations?

Centralized integration logic

Power Automate is effective for connector-driven business processes, while Martini can centralize reusable validation, canonical mapping, enrichment, routing, and multi-system orchestration across many flows.

Controlled APIs and workflows

Martini can consume Power Platform APIs, call protected HTTP-triggered flows, and expose REST APIs that Power Automate invokes. This creates explicit integration boundaries instead of embedding complex logic in individual flows or scripts.

Operational reliability

Martini workflows can provide durable checkpoints, correlation, idempotency, bounded retries, exception handling, and monitoring around Power Automate interactions and downstream systems.

Maintainable delivery

Reusable workflows, mappings, secure configuration, and environment-aware deployment reduce point-to-point coupling while preserving the flexibility to use Power Automate connectors and Microsoft services where they are most appropriate.

Frequently asked questions

How can Microsoft Power Automate be integrated with enterprise systems?

Microsoft Power Automate integrates through cloud flows, HTTP request and response endpoints, Power Automate and Power Platform REST APIs, connector-specific triggers, selected webhook-style callbacks, files, databases, Dataverse, and Microsoft or third-party services. The exact operations depend on the connector, environment, permissions, licensing, and target service.

Can Martini integrate with Microsoft Power Automate?

Yes. Martini can call Microsoft Power Automate HTTP-triggered flows, consume applicable Power Automate and Power Platform REST APIs, expose REST APIs for Power Automate to call, and orchestrate mapping, validation, retries, persistence, and downstream integration logic.

Do I need a connector to integrate Microsoft Power Automate with Martini?

No. A dedicated Microsoft Power Automate connector is not required. Martini can use Power Automate's HTTP-triggered flows, platform REST APIs, supported callbacks, and REST APIs exposed by Martini or by systems orchestrated through Power Automate.

Is there any extra Lonti cost to integrate Microsoft Power Automate with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Microsoft Power Automate. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Microsoft, Power Automate licensing, cloud infrastructure, or other third-party systems depending on subscription, usage, connector, and deployment model.

Which Microsoft Power Automate integration methods should be used?

Use Power Automate HTTP-triggered flows for explicit process boundaries, the applicable Power Platform REST APIs for platform administration and monitoring, and connector-specific triggers or actions for Microsoft and third-party services. Webhook-style support is available only for selected connectors, and there is no confirmed general-purpose native GraphQL or SOAP API.

Are events, webhooks, or callbacks available in Microsoft Power Automate?

Power Automate supports connector events and webhook-style triggers or callbacks for selected connectors and custom connector scenarios. Coverage, subscription lifecycle, payloads, and retry behavior are connector-specific; other connectors may use polling, recurrence, or service-specific mechanisms.

How does synchronization with Microsoft Power Automate work?

Synchronization can be event-driven through connector triggers or HTTP requests, or scheduled through recurrence and Martini workflows. Martini can map payloads to canonical models, follow paginated platform API results, store checkpoints and correlation identifiers, and use idempotent upserts to reduce duplicate processing.

How does Martini handle mapping, errors, and retries with Power Automate?

Martini workflows can transform Power Automate requests and responses, validate required fields, apply business rules, and route data to multiple targets. Transient failures and throttling can use bounded exponential backoff, while durable error handling, correlation IDs, checkpoints, and idempotency controls help isolate persistent failures and prevent duplicate actions.

Related Martini documentation

APIs

Workflows

Transformation

Security

Operations

Connect Microsoft Power Automate with Martini

Use Martini to connect Microsoft Power Automate HTTP flows and platform APIs with enterprise applications through secure workflows, reusable APIs, data mapping, business rules, and operational controls.

EXPLORE MARTINI
BOOK A DEMO