5 results found
-
Support Liquid and XSLT transformations for automation webhooks
Allow Flow Connect automations to transform webhook-trigger input and output using Liquid and XSLT transformers. This supports existing Flow Classic customers moving their integrations to Flow Connect.
8 votesThe feature request has been approved and is now scheduled for development. Our product team has determined that it aligns with our product roadmap and will bring value to our platform. We will keep you updated on its progress.
-
Option for Daylight Saving Adjustments in Addition to Static UTC for Scheduled Workflows
As a user, I would like the option for scheduled workflows to adjust for daylight saving changes, as the system currently only supports a static UTC setting. Adding this flexibility would accommodate different timing needs, allowing for both local time adjustments and consistent UTC scheduling.
4 votesWe are happy to inform you that development work has begun on your requested feature in Flow Connect. Our product team has assigned resources and is actively working on implementing it. We will keep you updated on its progress.
-
extend authentication options for Automations
Currently external systems can only authenticate with the Automation Access Key in x-api-key.
There are some systems that are limited to what they can send, like the IFS External Reporting Gateway:
Authorization Request Header format: "Authorization": ["Bearer <API Key>"]
Increasing the authentication options for our Automations, in this case changing the header name zo "Authorization", would enable some use cases for Flow around IFS Reporting
1 vote -
Copy Curl Command on Automations
It would be nice to have the ability to copy curl command from the automation settings in the Hub so that I could paste this into tools like Postman.
1 voteThank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
-
GET endpoint with URL params for an Automation
In many use cases we need to be able to expose a GET endpoint, using URL parameters as input to the Automation App.
One general use case is callbacks, where a callback from a service is usually made using an http GET request.
Specifically we will need this when doing online payments (using web browser) where the payment confirmation/receipt is sent using a callback GET with url params containing e.g. order id or payment reference.
1 voteThank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
- Don't see your idea?