refreshing adobe api credentials in power bi with power automate

[PrivateAnalytic]

So I am looking to use Microsoft Power Automate to refresh Adobe API Credentials every 13 days to mitigate a Power BI Refresh Failure every 2 weeks. Is this possible?

Ive done the following steps, but it appears it doesnt work successfully when the credentials actually expire.

Steps to Automate Adobe API Credential Refresh with Power Automate

1. Understand the API Requirements:

   • Check Adobe API documentation for how to authenticate and refresh tokens. Typically, this involves sending an HTTP request to an authentication endpoint with necessary credentials (e.g., client ID, secret, and refresh token).

2. Create a Power Automate Flow:

   • Log in to Power Automate and create a new flow.
   • Select a "Scheduled Cloud Flow" to set a recurring schedule.

3. Set the Recurrence Trigger:

   • Set the flow to trigger every 13 days. Use the "Recurrence" action and configure the interval accordingly.

4. Add an HTTP Action:

   • Use the HTTP action in Power Automate to send a POST request to Adobe's API authentication endpoint.
   • Include all required headers and body parameters in the request to refresh the token.

5. Parse the Response:

   • Add a Parse JSON action to handle the response from the Adobe API. Extract the new access token from the response.

6. Update Power BI or Another System:

   • If Power BI is fetching data using Adobe credentials, store the new token in a secure location (e.g., Azure Key Vault, Power Automate Environment variables, or SharePoint).
   • If necessary, update the token in Power BI's data source settings.

7. Test the Flow:

   • Run the flow manually to ensure it successfully refreshes the token and updates Power BI or the relevant system.

8. Monitor the Flow:

   • Use Power Automate’s monitoring tools to track runs and troubleshoot failures.

[abhinavpuri]

Hi @PrivateAnalytic ,

For Adobe Analytics APIs you can use OAuth based Server to Server credentials. These have defualt expiration set to "never expire" for client_secret. This way refreshing credentials is not required as long as fresh bearer_token is generated.