Approaching your first process flow
Last updated
Last updated
The flexibility of process flows means that there's no 'one size fits all' approach - everyone's requirements are different, and the scope is huge. This level of flexibility is a great advantage but on the flip side - where do you start?
Here, we outline the bare bones of a process flow so you know what to consider as a minimum when getting started for the first time.
A scratchpad area will be available soon. In the meantime, we suggest registering for a sandbox account and experimenting there.
Make sure you create instances with credentials for your third-party application sandbox accounts, rather than live ones!
In their simplest form, process flows are defined to receive data from one third-party application and send it to another third-party application, perhaps with some data manipulation in between. Key elements are summarised below.
Process flows allow you to build highly complex flows with multiple routes and conditions. Here, we're considering an entry-level scenario to highlight key items as you get started with process flows.
Process flow can be associated with three version types: draft, deployed and inactive. Before you get started building process flows, we advise reading our page to make sure you understand how this works.
Do you need to refine data in the current payload, before it's processed any further? In process flows, filters are defined using the shape.
Does the data you pull (i.e. the payload) require advanced manipulation before processing continues? If it does, and you have development expertise in-house, you can write and apply .
In process flows, existing payload-level custom scripts are added using the shape. This is an advanced feature - very often, standard are enough to sync data as needed.
Do you need to manipulate source field values before they are synced to the destination? If yes, will standard handle this - or are required?
In process flows, field mappings and (if required) are applied using the shape.
Have you for this/these application(s)?
Have you (or multiple instances) of this/these connector(s)?
In process flows, the data destination is defined by associating an instance with a shape.