We previously introduced the ability to add new credentials for a deployed recipe via an embedded page in a 3rd-party site or app. Today we introduce the ability to create an embedded page for editing credentials for a single recipe deployment. For this purpose we have created a new API endpoint GET /v2/recipe-deployments/:recipe_deployment_id
. This endpoint requires same permissions and scopes as in /v2/recipe/:recipe_id?include=recipe-deployments
.
Please visit API Docs for more details on this API endpoint.
For more informaition on Embedded recipe deployment please read this article.
We are introdusing POST /v2/flows/export-to-recipe
API Call. With this call you can:
This new, more powerful endpoint, replaces the old one - POST /v2/flows/${flowId}/export-to-recipe
. Please visit API Docs for more details.
Before, the Flow Queues page displays the components inverted according to the flow graph (e.g if graph contain fork or content-based router) and don’t display the step name, only the number.
Now we render step name on Flow Queues page (like on Flow Designer) and render flow graph at Flow Queues, Runlog Execution, Thread pages in the same way as at Flow Designer page.
FIXED bug, where the flow-queues page would not load directly after a draft-version of a previously published flow was published.
FIXED when the Credentials and Recipe page would not load in cases where the user did not have permission to access auth secrets. Now, the UI shows a message with an error.
2.0.0
Make Raw Request
Action1.1.1
Receive Messages Long Polling
trigger to SQS server timeout by default1.0.0
Raw Request
Action