web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Cannot add connector a...
Power Automate
Suggested Answer

Cannot add connector action to an agent

(0) ShareShare
ReportReport
Posted on by RR-25060910-0
I created a custom connector. Test worked fine from connector
I add it to agent it gives always below error. No way to debug.
There were some GET actions in connector which worked. The failure comes for a POST action
 
ErrorThis
Tool has encountered an error obtaining required dependencies. Please
re-create the component or restore from a backup to resolve the problem.
I have the same question (0)
  • Suggested answer
    Sunil Kumar Pashikanti Profile Picture
    Sunil Kumar Pashikanti 2,318 Moderator on at
     
    This is a known gap between Power Automate and Copilot Studio when using custom connectors.
    Since GET works and POST fails, it usually points to strict schema validation in Copilot Studio, not a connector issue.

    Most common causes:
    1. Missing static schema (primary reason)
    Copilot Studio requires fully defined request and response schemas.
    Avoid dynamic bodies. Use Import from sample to define a fixed JSON structure.
    2. Missing descriptions
    Ensure the POST action and all required parameters have clear summary/description. Copilot uses this for dependency mapping.
    3. Complex payloads
    Deeply nested JSON or unsupported formats can fail. Keep the payload flat where possible.
    4. Metadata issues
    Remove and re-add the action after updating the connector. Sometimes metadata caching causes this error.
    Workaround:
    If the POST is complex, wrap it in a Power Automate flow and call the flow from the agent.
    Summary:
    This error is caused by schema/dependency resolution issues in the POST definition, not runtime failure. Making the schema explicit and simple usually resolves it.
     
    ✅ If one of the responses here solved your issue, please mark it as Accepted so others facing the same problem can benefit as well.
    👍 If this or any other reply here helped you, feel free to give it a Like. It helps others and is always appreciated.

    Sunil Kumar Pashikanti, Moderator
    Blog: https://sunilpashikanti.com/posts/
  • Suggested answer
    RaghavMishra Profile Picture
    RaghavMishra 261 on at

    Hi there,

    Since your GET operations work and only the POST fails when wiring the custom connector into the agent, the most productive angle is to make sure the POST operation is fully and correctly defined as a tool. Here's what Microsoft Learn covers.

    Make sure the POST operation has complete request + response definitions

    • When you build a custom connector, each operation needs a defined request (including the body) and a defined response. The supported way to do this is the Import from sample option on the Definition tab, where you paste a sample JSON body/response so the connector generates the schema.
    • GET operations often have no request body, which is why they tend to "just work," whereas a POST with an undefined or dynamic body is more likely to fail validation - so this is the first thing worth confirming.

    Add the custom connector to the agent the supported way

    1. Open your agent, go to the Tools page, and select Add a tool.
    2. Choose New tool > Custom connector (this takes you to the Power Apps Custom connectors area), then select your connector.
    3. Set up the connection and submit. By default the connection uses user credentials; you can switch to maker-provided credentials if needed.

    Re-add after changes

    • If you edited the connector definition after first adding it, remove the tool and add it again so the agent picks up the current definition.

    References

    One honest caveat: the exact error you're seeing ("Tool has encountered an error obtaining required dependencies...") isn't described in Microsoft Learn, so I can't point to a documented root cause for that specific message. If the steps above don't resolve it, it's worth raising a Microsoft support ticket so the product team can look at the underlying dependency resolution.

    Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!

    Raghav Mishra - LinkedIn | PowerAI Labs

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Known issue with browser automation in Power Automate for Desktop on Google Chrome 146 and 147
Share your ideas and struggles with building Power Automate flows!
Survey: Power Automate mobile app
How to Ask for Help with Your Power Automate Workflow
Flows are not visible for users who sign in with their personal accounts
Start and wait for an approval action
Restore a deleted flow
List of actions cheat sheet for Power Automate Desktop
Welcome to the Power Automate forum!

Product updates

Microsoft Power Platform Community release plans