Ennis Al-AsaaedWe understand that customers want to automate manual processes and connect workflows, and to help accelerate that, we are considering options such as introducing an API, Webhooks, URL parameter connector/utility, and bi-directional integrations within Formstack Workflows (formerly Copilot).
Our goal is to enable customers to supply data to Workflows (formerly Copilot) from external systems and trigger workflows programmatically. This will enhance Workflows (formerly Copilot) for complex use cases.
Let us know what you think of this feature idea by adding comments below.
Disclaimer: The posts available here, including in the “Under Consideration” and “Planned” tabs, are the best reflection of what the teams are currently working on in each product. Unless located in the “Launched” tab, this is not a commitment to a specific feature or release date, but it should help you understand the priorities of each of our product teams.
Lacey JacksonAs part of our API Connector release for Formstack Workflows, we will be able to store data for 60 days, which will accommodate use cases where subsequent tasks may not be completed for 60 days. This will ensure that data pulled in via API is able to be mapped to future workflow steps for 60 days, and at that time will be purged. Note that information submitted in a workflow, including mapped fields containing values from an API, will remain visible to our customers in forms and documents upon the data being purged.