Flow email settings are now saved for each editor on a flow. Anyone who has edit access (via individual permissions or team permissions) on a flow can choose what kind of emails they want from that flow. You can choose to receive an email anytime the flow runs, just when it fails or pauses, or no emails at all (which is a new option!).
Access these settings from the settings view of a flow, or the settings modal from the Flows home page.
Flows that have the Pull from Email Attachment step and are triggered by inbound emails now can take advantage of a queue. If your flow is running when another email comes in, we will queue up that email to be processed in the next run. This is the same behavior that flows triggered by webhooks use.
The queue has been upgraded to allow any flow to queue up to 200 pending runs before any new runs are ignored.
Many APIs use OAuth2.0 to authenticate, which can be difficult to set up. The OAuth2.0 form (used by all three API steps) now has streamlined settings, along with a visual update. The simple version requires fewer fields to be configured and covers most APIs. The form also lets you toggle between the new simple version and the full custom version. When switching, values will be ported back and forth between the two forms.
We’ve made two new updates to the Filter Rows step that we think we add even more power to your flows.
Add multiple criteria to single filter
In the past, if you had a large list of criteria that you had to filter against, such as email domains to remove, you needed to add an individual rule for each criteria.
Now, the contains, not contains, is equal to, and is not equal to filter operations will accept multiple criteria fields.
Use merge tags in a filter criteria
Previously, when you needed to compare one column to another, and the filter based on that comparison, you would use an Insert If Else Column step to perform the comparison, followed by a Filter Rows step to then filter based on that comparison (also creating an extra temporary column in the process).
Now, the Filter Rows step will accept merge tags. Enter any column name, wrapped in {curly braces}, to compare columns inside of a filter.
Introducing Card Templates!
You can now build cards with steps and relevant documentation, and then save them as templates for anyone on your team to use. Card Templates are great for sharing common data sources, re-using parts of Flows, sharing documentation, and keeping Flows up to date across your team.
Some key things about Card Templates:
You can save any card as a Card Template to the sidebar. When a card is saved, you and everyone on your team can find it there and pull it into any Flow.
You can choose whether or not to shared authorized steps on a Card Template (think authorized Google Sheets, Shopify, database steps). This lets you more easily share team logins.
Once you pull in a Card Template to your flow, you are free to make any edits to it that you need. Consider Templates as a jumping off point!
Authors of a Card Template can push new update from any instance of that card. Anyone using that Card Template will be notified in their flow that the Template has been updated so that they can compare the new version to their current version before updating
We are thrilled to announce the launch of team folders! You can now create folders to easily organize and work on Flows with your team. Read about all of the changes in detail here.
We also completely redesigned the Flows page to make it easier to find, organize, and manage your Flows. What was previously one page is now three distinct spaces:
You’ll also notice that Flows are now displayed in rows, designed to make it easier to identify the Flow you’re looking for:
To get started, we recommend creating folders and moving Flows into your team space. This will enable you to create a shared organizational system for your entire team, and make it much easier to find and collaborate on Flows.
.png)
There’s lots more to come, so please send us your feedback and ideas!
We've updated the Enrich with an API and Send to an API steps to include an Error Handling settings section.
With these new settings, you can enable your API steps to pass through data even if some of the API requests fail. Modifying this setting will add new error handling columns to your dataset reporting on the status of those API calls.
Take your flows to the next level by routing rows with errors into branches to alert someone on your team about the errors, retry them, or anything else. Read more about it here.
Give your cards some personality and identity by adding emoji!
As a bonus, if you type in an emoji as the first part of a title, it will automatically be shifted into the emoji slot.
Placing steps into cards is even easier now!
We’ve improved our drop targets so that its easier to place steps inside cards. Cards are a great way to organize portions of your flows and leave notes and documentation.
The team is working on some more awesome features that will further build off of cards with steps inside of them, so stay tuned.
All API steps now offer the option to select the request type POST (GraphQL). With this request, you can insert your Graph query directly into the request body to specify the exact data that you’d like to pull from an API.
This enhancement makes it far easier to request data from popular GraphQL API endpoints such as Shopify, Facebook, and Monday.com along with many others.
Reference our How To docs for additional information.
We're making it easier for you and your teammates to share your Parabola Flows. Three big updates are launching today:
For all the details, check out our How To guide.
We're thrilled to announce that you can (finally) undo and redo changes in your Flows!
Any edits you make during a Flow-building session can now be quickly reverted. That includes adding, removing, or repositioning steps, updating step settings, changing step connections, and so on!
To use, simply type those keyboard commands you know so well:
Or, click on the arrows now located in the Flow navigation bar.
To undo or redo changes in step settings, you can use the same keyboard commands, or click the arrows at the top of the window.
We released several updates to our Flow builder navigation bar, so your workflow can be faster, clearer, and more collaborative.
Two new database integrations bring Parabola even closer to your data.
Our Pull from PostgreSQL integration now has its matching half! Use the Send to PostgreSQL step to automatically insert or update data in a PostgreSQL database.
We've also released a fresh integration with MS SQL Server, Microsoft's popular relational database product. Use the Pull from MS SQL and Send to MS SQL steps to create flows that connect directly to your database.
The two new Destination steps (Send to...) use connection pooling to drastically increase their speed. We extended this improvement to the existing Send to MySQL step, as well.
We've upgraded 8 of the most used, and sometimes slowest, transform steps! Most should run about 15x faster than they used to, which means if a step used to take 1 minute to finish, it will now only take 4 seconds.
The Pull from Shopify step has been updated to pull in more information when pulling in Product Inventory. Previously, it pulled only the available inventory for each item at each location – now, it also pulls information about the items themselves! Most notable is the addition of the Cost field.
Secondly, the Send to Shopify step has been updated to work with customer addresses. When creating or updating customers, mappings are now available for the primary address fields.
The "Pull from email attachment" step has been updated to forward any verification codes back to your inbox. Once you verify a Parabola email address outside of your domain, you can automatically forwardCSV attachments to trigger your flow.
We've made the steps sidebar collapsable! Now you can easily open and close it to get more space on your canvas, and stay in rhythm when you're building.
When the sidebar is closed, you can use the search keyboard shortcut ("s") to reopen it. The 'Help' button is always there for you.
Have you checked out our new Cards feature? Now you can easily add context to steps by using the rich text editor, improve the organization of your flow, and keep collaborators on the same page!
We've made some UI updates to our Pull from Shopify Step. Configure your settings with clearly defined headers, select the columns you want to pull in without needing a separate step, and filter products based on any set of conditions!
We pride ourselves as being the go-to tool for bulk data automation, and our new ability to import and export files through an FTP server only furthers that! Pull in CSV and Excel files, and work with larger data feeds including RSS and XML with our FTP integration.
.gif)
We've introduced more apparent tabs within the step settings at the top of the table, making it easier to explore input data from a previous step!
We've made some major performance updates to our Filter rows step. This step can keep or remove rows based on a set of conditions up to 15x faster.
For those of you working with larger datasets, the performance update should be a big improvement. Check out how fast we can filter through 100k rows of data!
Visual updates have been added to the builder including more consistent visuals and styling, larger arrows, intuitive text selection, and a single click to deselect steps. Tool tips have also been added to highlight any fixes to that need to be addressed in your flow. More improvements coming soon!
We’re excited to announce that the Send to Airtable step is now live! You can create, update, and delete records in your Airtable base without needing an API. Select the base and table that you want to send data to and map your Airtable field to the related column in Parabola.
We just launched our new design system for step configuration, codenamed "Metro" after Fritz Lang's silent sci-fi classic film, "Metropolis". Steps largely work the same, but you'll notice that the form elements that comprise them have received a major visual update. Our goal with this release (and the many that will follow it) is to make our steps look and work more consistently and to improve accessibility and learnability.
