Hi @JatinSaini ,
Thanks for reaching out to the Microsoft Fabric Community Forum.
@lbendlin providing useful information However, it appears that you are encountering an issue where the body is empty when running the API through the HTTP Connector via Power Automate. Please double-check the following steps to resolve this issue.
If the API returns an empty response body when triggering the pipeline, it could indicate.
- The API doesn’t directly give a Run ID or status information in the trigger response.
- The pipeline trigger request might be asynchronous. This means the triggering API call doesn't immediately give the Run ID, and you may need another API call to fetch it.
- Some APIs provide a separate endpoint to check recent pipeline runs or get details of an active run.
Note: Ensure that the API is meant to return a response body. Some APIs might only give a status code without a body.
Enable Response Logging in Power Automate.
- Check if the HTTP Connector in Power Automate logs headers or metadata in the response.
- Even if the body is empty, sometimes headers have extra details like an operation ID or a URL to check the run status.
- If the API gives an error status code (like 400, 404, 500), the response body may be empty or may have error details. Always look at the status code first.
- If the API needs authentication, make sure you're giving the right credentials (like an API key or OAuth token). An authentication failure can also result in an empty response.
Query for Recent Pipeline Runs.
- Use the API endpoint (if available) to fetch recent pipeline runs.
- Filter the results by trigger time, user, or other unique parameters to identify your specific instance.
Use a Custom Identifier in the Trigger Request
- When triggering the pipeline via API, some systems let you send custom metadata or tags as part of the request payload.
- For instance, you can include your username, a timestamp, or a custom tag (like Initiator: 'Your Name') in the request body.
- Use this metadata to query and differentiate your run.
Cors and Security Policies
- Cors Issues: If you're calling an API hosted on a different domain, Cross-Origin Resource Sharing (CORS) policies might stop the response from coming back. This is particularly important if you're using a custom connector.
- Firewall or Security Settings: Check if there are any firewall rules or security settings that could be blocking the response from reaching Power Automate.
- Use Postman or Curl: Test the API outside of Power Automate with tools like Postman or Curl to see if you get a response. This can help you figure out whether the issue is with the API or Power Automate.
For more information, please refer below link:
HTTP actions reference - Power Automate | Microsoft Learn
If my response solved your query, please mark it as the Accepted solution to help others find it easily!
And if my answer was helpful, I'd really appreciate a 'Kudos'.
