Import the Keysender custom connector into Power Automate or Azure Logic Apps so a flow can read your orders, stock, customers, and catalog, and act on them inside Microsoft 365. Connecting takes one extra one-time step, then it behaves like any other connection.
The Keysender custom connector for Power Automate is being published; the steps below apply as soon as it is available.
Make sure you have:
In the maker portal (make.powerautomate.com or make.powerapps.com), go to Custom connectors > New custom connector > Import an OpenAPI file, and upload the Keysender connector definition. You can also script this with paconn create.
Copy your api_key and api_secret from Account > Settings > API access in the panel.
Run Login once, on the connector's Test tab or in a throwaway flow, using your API key and secret. Copy the access_token from the response.
Choose New connection. In the API Key field, enter the word Bearer, a space, then the token.
Save the connection.
Run Get my account (identity + wallet). A 200 response with your name, email, and wallet balance confirms the connection.
api_key and api_secret.Submit a claim so Keysender Support can review it.
Power Automate has no built-in way to exchange a static key for a bearer token. So you run Login once with your API key and secret, copy the access_token, and paste the word Bearer plus the token into the API Key field. After that it behaves like any other connection.
Keysender has no outbound webhooks yet, so each trigger is really its matching action on a schedule. Add a Recurrence trigger, call the action, then filter for what is new in a Condition, usually by comparing against the highest id already processed. None of the triggers dedupe for you.
Your api_key or api_secret is wrong, not a connector bug. Recheck both under Account > Settings > API access and re-copy them exactly. If a later call returns 401, re-run Login and paste the fresh token, making sure it includes the word Bearer and the space.