You’re offline. This is a read only version of the page.
2
Hi,
We have been having some issues with one of our flows where a custom connector does not seem to work.
We bought a pack of Per-Flow Licensing and attached it to the Flow.
We then created a custom connector to connect to an internal web app to drop the users' response. We seem to be getting an error when testing the connector on it's own.
"Operation failed (400), see response below"
"message": "Invalid token\r\nclientRequestId: 61f309d8-db69-4e94-bfb5-468d-2580eee6"
What can I do having the per-flow license. We were under the impression that we can utilize custom connectors "Premium" but seems that every time we try to create a new one we get prompted for the start free trial of services. How should we go about and dealing with premium connectors if we can't from the context of our own accounts. Do they have to be created from within the flow?
We also do have a gateway in place but should users having the only "allowed to use" be able to see it within their flow? While testing we had to give the user admin access.
Thanks in advance.
I'm not sure if this is your problem, but I suspect it might be. To create Custom Connectors I believe you need to have a full Per User license. Once the connector is in use in the flow then you should be able to use the connector using the per flow licensing. But I don't think you can build flows using per flow licensing, just consume them.
Share
Report
All responses (
Answers (
