12 minIntegration
Power Automate Integration
Import the ABM.dev custom connector to build enrichment flows across the Microsoft 365 ecosystem.
In this guide
- Import the ABM.dev custom connector
- Configure API key authentication
- Build an enrichment flow with triggers and actions
- Integrate with Microsoft 365 services
Prerequisites
- An ABM.dev account with an API key
- Microsoft 365 or Power Automate license
- Power Automate maker permissions
1
Import the custom connector
Power Automate custom connectors let you call any REST API from your flows. ABM.dev provides an OpenAPI spec you can import directly.
- 1.Download the ABM.dev OpenAPI spec from your Settings → API Keys page
- 2.In Power Automate, go to Custom Connectors → New → Import an OpenAPI file
- 3.Upload the spec file and name the connector "ABM.dev"
- 4.On the Security tab, set Authentication type to API Key and parameter name to
x-api-key
2
Create a connection
After saving the connector, create a connection to authenticate your flows.
- 1.Click Test on the connector page, then New connection
- 2.Paste your ABM.dev API key and click Create connection
- 3.Test the connection with a "Get Me" action to verify it returns your account details
OpenAPI connector test
curl -X GET https://api.abm.dev/v1/me \
-H "x-api-key: YOUR_API_KEY"3
Build an enrichment flow
Create an automated cloud flow that enriches new rows from SharePoint, Excel, or any Microsoft data source.
- 1.Create a new Automated cloud flow
- 2.Add a trigger, such as "When a new row is added" in SharePoint or Excel
- 3.Add an ABM.dev Create Enrichment action and map the email field from the trigger
- 4.Add follow-up actions: send a notification via Outlook, update a row in Dynamics 365, or post to a Teams channel
Authentication
The custom connector uses API key authentication. Enterprise customers can request OAuth connector support by contacting ABM.dev sales.
Troubleshooting
Connector import fails
- • Ensure the OpenAPI spec version is 3.0 (Power Automate does not support 3.1)
- • Remove any unsupported features like
oneOforanyOffrom the spec - • Try importing the JSON version instead of YAML
Flow errors
- • Verify your API key is correct and has not expired
- • Check ABM.dev rate limits if you see 429 responses
- • Use the flow run history to inspect request and response payloads