Zapier provides a no-code automation & integration platform that makes it easy for web applications & software vendors to build integrations. With Zapier, it's easy to create workflows across different applications - automating recurring tasks, where users can set up "rules" that set up the flow of data between different tools and services.
Zapier workflows are called Zaps, and these are built up of a Trigger (an event that starts the flow) and one or more Actions. There is a catalog of thousands of connected apps & products that can be used in your Zaps.
The Convious-Zapier integration consists of a Trigger called New Order. What this trigger does is poll for newly created Convious orders, and making them available to be sent or used in other tools.
Getting started
Requirements:
-
A Convious API client, with access to a specific partner account. This can be requested through our support team.
-
A Zapier account, and most likely a paid subscription. Zapier offers a free tier, but this only has 100 zap task runs per month. By default, zaps run once every 15 minutes which equates to ~3000 runs per month. Only runs that pull in new Convious orders count towards your Zapier task limit. For advice on what Zapier subscription you will need, reach out to your customer success manager.
Configuration:
Step 1 - Create a new Zap and search the catalog for the Convious trigger
Step 1 - Select "New & Updated Orders" Event
Step 2 - Configure your account, using your API client details
Step 3 - Configure trigger settings
The Convious "New & Updated Orders" trigger has the following fields:
- Status - this setting will determine which order statuses will be pulled through the integration. We suggest to set this field to "confirmed", unless you have specific use for also receiving orders with status "open" (unfinished orders) and status "cancelled" (which includes refunded orders).
- Email, product type, From Visit Date, To Visit Date, Products, Reseller ID, Include - these settings control how data is filtered and what fields are returned, more details can be found in our API documentation. By default, these fields should be left blank to pull through all orders.
- Additional Account Slug(s) - this field can be used to pull orders from multiple Convious account slugs in one Zap. To use this functionality, you'll need to have a Convious API client that is set up with permissions for all the account slugs that you will to pull orders for. You'll then need to use one of these account slugs in the previous authentication step, and add the other accounts in this field.
Step 4 - Connect another system
The data from new & updated orders can now be sent to any other product or app that has an action in the Zapier catalog. For example, it is possible to send all orders to a Google Sheet. Using the Zapier Google Sheets integration, fields from a Convious order can be mapped to columns to capture relevant data.
Notes
- The integration will check for new events in the last 30 minutes on every run. This means that if the task is disabled for more than 20 minutes, you will likely experience a gap in the orders retrieved. It also means that the integration is not meant for historical order retrieval. If you have a need to retrieve historical data from Convious, please reach out to our support team.
-
Note that this integration is built against the Convious orders timeline API, which will return an order again if it has been updated. Since updated orders can contain updated (relevant) information, we will return these updated orders as new records. Workflows should be set up to expect orders to come through multiple times, and where needed override older order information.