Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This page includes video demonstrations showing different aspects of the Patchworks platform.
Watch our two-minute explainer video for Patchworks!
Our CTO, Conor Barr, demonstrates using our pre-built Blueprints , Connector Builder Postman Importer & no-code/low-code canvas with ready-to-use process flows, how quickly and easily you can cut down on implementation time and get your systems connected.
Our CEO, Jim Herbert, shows how easy it is to build your own custom connector with the Patchworks connector builder in just 5 minutes!
Our CTO, Conor Barr, demonstrates the power of flow control and cache shapes in Patchworks process flows.
Patchworks is an Integration Platform as a Service (iPaaS).
Our secure, multi-language, cloud-based platform automates the flow of data between your company’s business-critical systems/applications in a smart, intuitive way.
In today's market, businesses can pick and mix from best-of-breed applications to tackle specific goals...perhaps an eCommerce application for sales order processing; an ERP system for records management; a warehouse management system to maintain inventory and a CRM for relationship management and marketing.
On their own, these applications fulfil their individual requirements perfectly. However, the key to real strategic advantage is integration - establishing a frictionless exchange of data between all of your applications, in a smart way.
Watch our two-minute explainer video for Patchworks!
Historically, many businesses have gone down the API route to integrate systems - building and maintaining direct APIs in-house. This can be a costly exercise carrying an administrative burden, and a potential drain on resources - assuming you have the resources in the first place.
In contrast, Patchworks provides a cost-efficient way to streamline your operations via one, centralised platform - your integrations hub, if you will. Using our intuitive dashboard, you can add, manage and orchestrate your integrations with complete peace of mind when it comes to security and scalability.
Patchworks is an incredibly powerful no-code/low-code platform with everything you need to add and manage your integrations.
We know that integration requirements are often highly complex and a real challenge for customers - but we don't think the solution should be. A huge amount of thought has gone into making our no-code/low-code dashboard as smart and user-friendly as we can.
Using click-and-drop process flows with automated shapes and an impressive library of prebuilt connectors (in the Patchworks marketplace) and blueprints (from the Patchworks website), you can create powerful data flows, in a matter of minutes. You can adjust default field mappings and transformations as needed, trigger syncs, watch syncs run in real-time, view historical data, and troubleshoot issues - all without a single line of code.
With Patchworks, you can configure and connect any of our prebuilt connectors in process flows.
But what if we don't have a prebuilt connector for an application that you need to sync? Maybe you have a bespoke, in-house system - or perhaps you want to integrate an application that's completely outside of the eCommerce arena. No problem - the Patchworks connector builder is your new best friend!
If you have technical knowledge of APIs and working with data structures, you can use the connector builder to integrate any application with REST or SOAP APIs.
Speaking of technical expertise...
'Out of the box', Patchworks includes everything you need to manipulate and then exchange data securely between different third-party applications, securely and intuitively. However, for users with in-house development expertise and more complex requirements, advanced tools are available that you can use to take your integrations to the next level:
Use the Patchworks API to build against Patchworks from third-party systems and interact with your Patchworks process flows or services.
Custom scripting can be used at the field level (to build highly complex transformations for mapping individual fields) and at the payload level, so you can manipulate an entire payload before it is sent to the next element of your process flow.
Patchworks is proud to be a member of the MACH Alliance, and certified for ISO/IEC 27001:2022.
If you're new to Patchworks and want to find out more before you get started, take a look through this section for background information and demo videos.
A Patchworks blueprint contains everything you need to perform a specific task - for example, to sync orders from TikTok Shop to Shopify; to sync customers from Shopify to HubSpot, etc.
For more information please see: Blueprints.
See process flow canvas.
Having registered for a Patchworks account, use your credentials to log in to the Patchworks dashboard. This is where you can access everything you need to set up and manage data exchanges between third-party applications.
For more information please see: Patchworks quickstart guide.
The meaning of connector varies, depending on whether you are using process flows or services to sync data in Patchworks. Please expand the appropriate definition below.
If you need to integrate a third-party application that doesn't have a prebuilt connector in the Patchworks marketplace - and if you have technical knowledge of APIs and working with data structures - you can use the connector builder to integrate any application with REST or SOAP APIs.
For more information please see: Connector builder.
An instance is the mechanism that Patchworks uses to configure a connector for use in process flows - it's how we store your system credentials for a given connector in a single, easy-to-manage place.
You can add as many instances of a single connector as you need. For example, if you've installed the Shopify connector, you would go on to add one instance of this connector for every Shopify store that you need to sync using process flows.
For more information please see: Connectors & instances.
With Patchworks, you can install and then use instances of a range of curated, prebuilt connectors which are available from the Patchworks marketplace.
Typically, when we talk about Patchworks in this documentation set, we're referring to the Patchworks Integration Platform as a Service (iPaaS), which is accessed via the Patchworks dashboard.
Introduced in June 2023, the process flow feature is a completely new way to define if, when, what, and how data is synced between your third-party applications.
Process flows are built by dragging and dropping automated shapes onto a canvas, and then configuring them as required.
For more information please see: About process flows.
The canvas includes everything you need to build a process flow. Here, you drag shapes from the shapes tray, drop them onto the canvas, and then configure settings and relationships as required.
For more information please see: The process flow canvas.
When you add/edit a process flow, a set of shapes is available from the canvas. Each shape performs a specific task - for example, the trigger (schedule) shape is used to define a schedule upon which the process flow runs. Having dropped a shape onto the canvas, you can configure it with the required settings for that process flow.
For more information please see: Process flow shapes.
Process flows include all the functionality of services and much more. You can continue to use services but if you'd like to try process flows, please contact your Customer Success Manager, or reach out to [email protected].
If you registered for a Patchworks account after July 2023, you will be using process flows automatically.
See process flow shapes.
When working with services to sync data in Patchworks, a system is a Patchworks integration for a third-party business system - for example, Shopify.
The concept of 'systems' is only relevant if you use Patchworks services to sync data - it is not used in process flows.
You can work with the Patchworks dashboard in your preferred language, using the language switcher in the top information bar - for example:
When you switch languages, the dashboard fields, labels, buttons, and options are translated.
The following languages are currently supported:
English
French
German
Italian
Japanese
Netherlands
Portuguese
Serbian
Spanish
A cutting-edge iPaaS platform requires a robust, versatile infrastructure that scales with its customers. The Patchworks infrastructure is built on Kubernetes, a technology that has revolutionised how we deploy, manage, and scale our applications:
Flexible auto-scaling is a significant advantage for Patchworks users - it means you don't pay for a predetermined capacity that might only be required during peak periods, such as Black Friday.
Our flexible, auto-scaling architecture gives peace of mind by allowing you to start on your preferred plan, with the ability to exceed soft limits as needed. If you require more resources, you can transition to a higher tier seamlessly, or manage overages with ease.
Auto-scaling adjusts computing resources dynamically, based on demand - ensuring efficient, cost-effective resource management that's always aligned with real-time demand. The auto-scaling process breaks down into four stages:
At Patchworks, every process flow shape has its own microservice and its own Kubernetes pod(s). The diagram below shows how this works:
Metrics for Kubernetes pods are scraped from Horizon using Prometheus. These metrics are queried by KEDA and - when the given threshold is reached - auto-scaling takes place. This process is shown below:
Prometheus JSON exporter scrapes Horizon metrics for each Core microservice count.
Prometheus scrapes metrics from the JSON exporter.
KEDA queries Prometheus, checking if any Core microservice has reached the process threshold (set to 8).
If the process threshold is reached, KEDA scales the Core microservice pod.
The Kubernetes cluster auto-scaler monitors pods and decides when a node needs to be added. A node is added if a pod needs to be scheduled and there aren't sufficient resources to fulfill the request. This process is shown below:
The Kubernetes scheduler reads the resource request for a pod and decides if there are enough resources on an existing node. If yes, the pod is assigned to the node. If no, the pod is set to a pending
state and cannot start.
The Kubernetes auto-scaler detects that a pod cannot schedule due to a lack of resources.
The Kubernetes auto-scaler adds a new node to the cluster node pool - at which point, the Kubernetes scheduler detects the new node and schedules the pod on the new node.
With customers worldwide relying on Patchworks to sync data between numerous systems, we understand just how vital data security and integrity are throughout our operations. Patchworks is committed to implementing and promoting Information Security best practices at every level of our organisation.
Following rigorous audits by an accredited certification body, we are delighted to see this reflected in our certification for compliance with ISO/IEC 27001:2022.
is the most recent update of the international standard for managing information security.
Published by the , it provides a framework for establishing, implementing, maintaining, and continuously improving an Information Security Management System (ISMS). This defines how Patchworks manages security in a holistic, comprehensive manner.
To confirm our certification, scan the QR code above, or check the link below!
A connector is the mechanism that Patchworks uses to configure a system for use in services - it's how we store your system credentials in a single, easy-to-manage place. For more information please see: .
A service is the original Patchworks mechanism for defining if, when, what, and how data is synced via Patchworks. If you registered for a Patchworks account before July 2023, you'll be familiar with using to sync data between systems.
For more information please see: .
Having registered for a Patchworks account and logged into the dashboard, you're all set to start syncing data between your business-critical systems. There are two ways to approach this:
Process flows are a new, incredibly powerful tool that you can use to define smart, flexible flows to exchange data between connector instances. Process flows are built by dragging and dropping shapes onto a canvas, and then configuring those shapes to work in the way you need. Please take a look at our Patchworks quickstart guide to get your bearings, and then navigate to the process flows section of this documentation for more detailed information.
​
The Patchworks infrastructure is designed for resilience and scalability - utilising cutting-edge technologies and best practices to ensure your data flows securely, efficiently, and reliably.
Leveraging a combination of proven technologies and innovative solutions, our tech stack is curated to provide a comprehensive, flexible environment for developing, deploying, and managing our Core product.
In this section
There are two possible paths for new clients to get up and running with Patchworks:
Custom integrations, with help from the Patchworks team
Self-serve integrations, via the Patchworks dashboard
If yours is a custom integration, you're in safe hands! Our teams will work with you to gather requirements and implement a tailor-made solution to meet your exact needs. However, with the launch of the new Patchworks dashboard, self-serve onboarding is now possible.
In this guide, we summarise the key steps required to get up and running, with links to relevant articles to help you complete each one.
Key steps from initial registration through to putting process flows live are summarised in the illustration below:
To register your company for a Patchworks account so you can access the Patchworks dashboard, use our registration link below:
If your company is standalone and you don't need to manage other (linked) companies, you won't need to complete any further company setup.
Having registered for a Patchworks account, a user account is created with the credentials you provided. By default, this is an admin account.
Different organisations have different needs when it comes to utilising the Patchworks dashboard - from minimal features required to perform specific tasks, all the way through to advanced functionality for building complex data flows in-house.
Our Core subscription tiers ensure that there's something to suit everyone. Information on this page details available subscription tiers and associated information.
Having , its associated features and allowances are available to your organisation. Each user within your organisation is assigned a which determines if/how they can access these features.
The table below summarises available dashboard features and feature allowances for each Core subscription tier.
The table below summarises feature access and allowances for each Core subscription tier.
If you have come to Patchworks via an agency/partner, please contact them to arrange your preferred subscription.
Subscription tiers are associated with different allowances for the number of deployed connectors, and the number of deployed process flows.
For allowance purposes, a 'deployed' process flow is a process flow that is both deployed and enabled. A 'deployed' connector is a connector that is in use by a 'deployed' process flow.
To view the number of 'deployed' connectors and the number remaining in your subscription tier allowance, select connectors and instances from the left-hand navigation menu - your allowance status is shown in the header of the manage connectors page:
To view the number of 'deployed' process flows and the number remaining in your subscription tier allowance, select process flows from the left-hand navigation menu - your allowance status is shown in the header of the manage your flows page:
Leveraging a combination of proven technologies and innovative solutions, our tech stack is curated to provide a comprehensive, flexible environment for developing, deploying, and managing our products.
Our user interface combines the power of PrimeVue for feature-rich UI components, Tailwind for styling, and Vue.js for building a progressive and interactive user experience.
Laravel is a PHP framework known for its elegant syntax and robust features. Combined with Nuxt - an open source framework based on Vue.js, Nitro, and Vite - we have a solid foundation for server-side rendering and seamless navigation.
We leverage the agility and scalability of Amazon Web Services (AWS) for cloud infrastructure, Vercel for seamless deployment and hosting, Kubernetes for container orchestration, and Argo for managing and automating workflows.
Our development process utilises TypeScript for type safety, PHPUnit for comprehensive testing, NPM for efficient package management, and Docker for containerisation.
We use MariaDB and MySQL for relational database management, Elasticsearch for powerful search and analytics, and Redis for high-performance caching and data storage.
Registering a new company will create you as its administrat
For simple registration, you provide an email address and a password to use as login credentials for the Patchworks dashboard, followed by a few company details.
Your account is then created with immediate access to a free trial which runs for 15 full days (ending at midnight on the 15th day).
Step 1 Access the and click the register option:
Step 2 Complete user details for the admin user to be associated with this account, then click continue:
The email address provided here is used to create a Patchworks admin account. When setting your password, the following rules apply:
A minimum length of 8 characters
At least 1 lowercase letter (a - z)
At least 1 uppercase letter (A - Z)
At least 1 number (0 - 9)
At least 1 special character (!, $, #, or %)
Step 3 Complete company details for the admin user to be associated with this account, then click continue:
The email address provided here is used as the Patchworks point of contact for your company. The address defaults to the same email account that you specified for the user account in the previous step, but you can change it if necessary.
Step 4 Read and accept the Patchworks terms & conditions, then click create Patchworks account:
New companies have immediate access to a free trial which runs for 15 full days (ending at midnight on the 15th day).
When setting a password for , the following rules apply:
A minimum length of 8 characters
At least 1 lowercase letter (a - z)
At least 1 uppercase letter (A - Z)
At least 1 number (0 - 9)
At least 1 special character (!, $, #, or %)
Password validation includes checks to determine if the password specified for registration or reset is compromised.
Checks are made using the haveibeenpwned.com service with the k-anonymity model, to determine if a password has been leaked. If a specified password is found to be compromised, it cannot be used and you will be prompted to try again.
Patchworks passwords do not expire.
Users who sign in via Patchworks can choose to any time, from the Patchworks sign-in page. Alternatively, users with a Client Admin role can .
Patchworks passwords are stored in an encrypted AWS database.
Passwords can never be viewed or accessed by users, irrespective of their role.
Password reset links are valid for 24 hours. After this, another password reset must be triggered so a new link is emailed.
Passwords are never set on behalf of other users.
Users can reset their password via a forgot your password link - this link is always available at the bottom of the sign in to Patchworks page:
Selecting this option displays a reset password page, where the user can enter their email address and trigger a password reset email:
The password reset email includes a link for the user to follow and reset their password.
Password reset links are valid for 24 hours. After this, another password reset must be triggered so a new link is emailed.
However, if a password reset is triggered for a Google sign-In user, they still receive a password reset email, which can be used to set a Patchworks password.
However, OAuth2 is also used for clients who wish to access Patchworks services via a Patchworks API endpoint. In this scenario, Patchworks provides an access token to clients, which is used to authenticate API requests.
Two registration paths are available for Patchworks - whichever you choose determines how users access the platform:
Users . Thereafter, these credentials are used to sign into Patchworks:
Google Sign-In is implemented using the OAuth (Open Authorisation) protocol.
Two versions of OAuth are available - OAuth 1.0 and OAuth 2.0. The Patchworks implementation uses OAuth 2.0.
OAuth enables users to log into an application/website (the Client/Consumer - in this case, Patchworks) using account information from another application/website (the Service Provider - in this case, Google) without ever sharing the user’s password. This is known as Secure Delegated Access.
To achieve this, OAuth uses a system of access tokens. An access token authorises temporary access to specific account information - Patchworks requests and stores the following details from Google:
UserID
Name
Email address
Avatar URL
The Google sign-in flow for a user is summarised below:
The user selects Sign in with Google.
Patchworks redirects the user to the Google Sign-In page. Here, the user is informed what information they will share with Patchworks by signing in to Google.
The user enters their Google account credentials. If sign-in is successful: - The Google Authorisation Server issues an access token to Patchworks. - Patchworks requests required data from Google, presenting the access token for authentication. - Google returns the requested resources (provided that the access token is valid).
The user is returned to Patchworks and is logged into the dashboard.
Passwords can never be viewed or accessed by users, irrespective of their role.
Any logged-in user can change their password by selecting the Change password option associated with their avatar (in the top right-hand corner of the dashboard).
Password reset links are valid for 24 hours. After this, another password reset must be triggered so a new link is emailed.
Passwords are never set on behalf of other users.
Users can reset their password via a Forgot your password link - this link is always available at the bottom of the Sign in to Patchworks page:
Selecting this option displays a Reset Password page, where the user can enter their email address and trigger a password reset email:
The password reset email includes a link for the user to follow and reset their password.
Password reset links are valid for 24 hours. After this, another password reset must be triggered so a new link is emailed.
However, if a password reset is triggered for a Google sign-In user, they still receive a password reset email, which can be used to set a Patchworks password.
A minimum length of 8 characters
At least 1 lowercase letter (a - z)
At least 1 uppercase letter (A - Z)
At least 1 number (0 - 9)
At least 1 special character (!, $, #, or %)
Password validation includes checks to determine if the password specified for registration or reset is compromised.
Checks are made using the haveibeenpwned.com service with the k-anonymity model, to determine if a password has been leaked. If a specified password is found to be compromised, it cannot be used and you will be prompted to try again.
Patchworks passwords do not expire.
Patchworks passwords are stored in an encrypted AWS database.
However, OAuth2 is also used for clients who wish to access Patchworks services via a Patchworks API endpoint. In this scenario, Patchworks provides an access token to clients, which is used to authenticate API requests.
How to create a Patchworks account
Two registration paths are available for Patchworks:
You must complete the process if you want to log in with your Google account credentials. If you provide a Google email address as part of the process, this will be associated with a Patchworks password.
This section includes information to help with whichever registration path you choose.
If you are a Patchworks partner managing , you can add linked company profiles after your own company is set up.
For more information please check our section.
If you registered for a Patchworks account before July 2023, you'll be familiar with using to sync data between systems. Process flows include all the functionality of services and much more. You can continue to use services but if you'd like to try process flows, please contact your Customer Success Manager, or reach out to [email protected]. If you registered for a Patchworks account after July 2023, you will be using process flows automatically.
If you are an existing customer, you'll be familiar with the concept of using services to exchange data between two system connectors. If you're not ready to make the switch to process flows, that's OK - please see the section of this documentation for information that's relevant to your way of working.
You can register with a Google sign-in, or with a username and password. For details, please see: .
If you are a Patchworks partner managing multiple company profiles, the should be enabled for your account. With this in place, you can .
If your company DOES need to manage other companies in Patchworks and the is enabled for your account, you can .
As an admin user, you can choose to create additional user accounts so other members of your team can access the Patchworks dashboard. When you create a user account, you can choose whether that person will have admin privileges (so they can create and manage process flows in Patchworks), or simple user permissions, (so they largely have view-only access). For details, please see .
To learn more about Patchworks roles and permissions, please see: . If you are adding/updating users for a managed company profile, please see s.
With your Patchworks company profile in place and users created, you're ready to start creating process flows. There are two approaches for this - , or .
A includes everything you need to sync data between two systems - i.e. , , , , . Having purchased and installed a blueprint from the (following installation instructions provided) - process flows are then ready to test and subsequently put live.
Here, you add/install/build all required resources - i.e. , , , , , and any other resources needed to perform given tasks. Note that the Patchworks marketplace includes a library of connectors, process flows, scripts and cross-reference lookups that you can install and use as-is, or edit to meet specific requirements. If we don't have a prebuilt for an application you need to sync and you have some technical expertise in-house, you can use the to build your own.
Once a process flow is activated, it runs automatically as per any defined settings. if required, you can also choose to , with instant feedback and real-time logging.
As a process flow runs, you can see real-time progress from the , with detailed logs generated throughout the run. can also be viewed retrospectively, so you always have full oversight of what's happened with your data.
The blueprint store tier is for users who only need dashboard access to run . These blueprints are built to perform specific tasks and as such, access is limited to features directly associated with purchased blueprints. The table below summarises allowed feature access for users on the blueprint store tier.
Advanced features are available on the , or can be added for users via a . These features are listed below.
The table below summarises bolt-ons that can be purchased and added to .
The partner features bolt-on allows you to . An allowance is provided for the number of companies created for given subscription tiers.
Anyone can sign up for a new Patchworks via our . When your 15-day trial period ends, you can contact the Patchworks Sales team to purchase the required subscription. The quickest way to do this is via live chat in your dashboard:
If you provide a Google email address as part of the process, this will be associated with a Patchworks password. If you want to log in with your Google account credentials, you should complete the process instead.
Step 5 Your Patchworks account is created, and you'll receive a welcome email. You can now lusing the email address and password that you provided.
Any logged-in user can change their password by selecting the change password option associated with their avatar (in the top right-hand corner of the dashboard). For further information please see: .
Users associated with an can trigger a password reset for any users in their company profile, via the Patchworks dashboard. For more information please see our page.
If a user registers their Patchworks account with , they won’t be aware of a ‘Patchworks password’ because they always sign in with Google credentials.
This does not affect the person’s Google sign-in, it just means they can choose to log in via Google or enter their email address and Patchworks password ().
We have already noted that is used to authorise access to Patchworks via . In this scenario, Patchworks requests an access token from Google; once a token is received, it is used to request the required user information for the sign-in process.
For further information please see our .
For further information, please see the help page.
Users . Thereafter, signing into Patchworks is via Google:
For further information, please see the help page.
The user accesses the .
Within Patchworks, user accounts are associated with a role. This role determines the level of access that users have within the Patchworks dashboard (subject to the active ). For more information please see the page.
Passwords can never be viewed or accessed by users, irrespective of their role. For further information please see the section.
For further information please see: .
Users associated with the client admin role can trigger a password reset for any users in their company profile, via the Patchworks dashboard. For more information please see our page.
If a user registers their Patchworks account with , they won’t be aware of a ‘Patchworks password’ because they always sign in with Google credentials.
This does not affect the person’s Google sign-in, it just means they can choose to log in via Google or enter their email address and Patchworks password ().
When setting a password for , the following rules apply:
Users who sign in via Patchworks can choose to any time, from the Patchworks sign-in page.
Alternatively, users with a Client Admin role can .
We have already noted that is used to authorise access to Patchworks via . In this scenario, Patchworks requests an access token from Google; once a token is received, it is used to request the required user information for the sign-in process.
For further information please see our .
Marketplace
Access restricted to viewing/updating connectors included with purchased blueprint(s).
Connectors
Add new instances for existing connectors
Edit existing connector instances
Process flows (general)
Run logs
Edit existing process flow settings
Edit existing process flow variables
Deploy existing process flows
Enable & disable labels for existing process flows
Add & delete labels for existing process flows
Add & delete email notifications for existing process flows
Run existing process flow manually
Process flows (shapes) - trigger
Edit the trigger schedule for existing process flows
Process flows (shapes) - connector
Edit instance
Edit existing parameters & filters
Process flows (shapes) - filter
Edit existing filters
Process flows (shapes) - route
Edit existing condition filters
Process flows (shapes) - add to cache & load from cache
Can use if included with process flow(s)
Cannot create new caches
Cannot delete caches
Can clear existing cache(s) via cache maintenance
Process flows (shapes) - de-dupe
Can use if included with process flow(s)
Cannot create new data pools
Cannot delete data pools
Can remove single IDs via data pool maintenance
Patchworks API
Can use if required by purchased blueprint(s)
Webhooks
Can use if included with process flow(s) - cannot add new webhooks
Event connectors
Can use if included with process flow(s) - cannot add new event connectors
Custom scripts
Can use if included with process flow(s) - cannot add, edit, delete or deploy scripts
Cross reference lookups
Edit cross reference values in any cross reference lookups associated with purchased blueprint(s)
Connector builder
No access
Cache
De-dupe
Custom scripts
Webhooks
Events
Patchworks API
Advanced features
Enable advanced features
Single connector
Add one more connector to current deployed connectors allowance
10 process flows
Add ten more process flows to current deployed process flows allowance
60 webhooks per minute
Add 60 webhooks per minute to existing rate limit.
10,000MB payload size
Increase the maximum size for any payload used in a process flow by 10,000MB. The default allowance is 500MB.
Partner features
Create linked companies
Flow concurrency limit
Increase the number of process flows that can be run concurrently.
Cache memory (MB)
Increase the size of caches that can added. The default allowance is 50MB.
Inbound API rate limit
Increase your rate limit for the Patchworks API.
Trial
Having registered for a Patchworks account your free trial starts with full access to all dashboard features for 15 days.
Blueprint Store
Applies for customers who access the Patchworks dashboard purely to use a particular blueprint - i.e. there's no requirement to install additional connectors/resources, build/update process flows, etc. With some exceptions, blueprint store user access is read-only.
Standard
Standard tier users have full access to all standard dashboard features - advanced features are displayed but are read-only. Limits apply to the number of deployed connectors and process flows allowed - if required, bolt-ons can be added to extend these allowances.
Professional
Professional tier users have full access to all standard and advanced dashboard features. Enhanced limits apply to the number of deployed connectors and process flows allowed - if required, bolt-ons can be added to extend these allowances.
Custom
Custom tier users have full access to all standard and advanced dashboard features. Custom limits apply to the number of deployed connectors and process flows allowed.
Full access
No access
Full access
Full access
Full access
Full access
No access
Full access
Full access
Deployed connectors (i.e. connectors used in enabled & deployed process flows)
2
Read-only access to purchased blueprint connectors
2
4
Custom
Unlimited
Unlimited
Unlimited
Unlimited
Unlimited
2
10
20
Custom
1
10
10
20
Starting at 30
Operations (per month)
10,000
150,000
250,000
500,000
Custom
Full access
No access
Full access
Full access
Full access
Patchworks API (per minute)
240
240
240
Starting at 240
Webhooks (per minute)
2
0
120
Starting at 120
Full access
No access
Full access
Full access
Email notifications (per month)
100
100
500
1000
Starting at 1000
Username and password
User accesses the Sign in to Patchworks page. Here, they select the register option and then provide an email address to be associated with their account, together with a password.
Google sign-in
User accesses the Sign in to Patchworks page. Here, they select the register option and enter an email address to be associated with Google Sign On. An email is sent to this address, containing a link to trigger the Google registration process.
Having registered for a Patchworks account, a company profile is created for your organisation. From here you can view/update basic details for your organisation (name and contact information) and manage users.
As the user who registers a company for a Patchworks account, you are granted administrator access to the dashboard. This is is the highest level of access that can be associated with a company profile.
If you are an agency/partner with permissions to manage multiple companies, company profiles work a bit differently. Please refer to our Multi-company profiles section.
Simple
Basic Auth
Username and password
User accesses the Sign in to Patchworks page. Here, they enter the email address associated with their account, and a password.
OAuth 2.0
Google sign-in
User accesses the Sign in to Patchworks page. Here they select the Sign in with Google option for redirection to the Google sign-in page.
For Google account registration, you are directed to Google for authentication. Your account is then created with immediate access to a free trial which runs for 15 full days (ending at midnight on the 15th day).
Step 1 Access the Patchworks login page and click the register option:
Step 2 Enter your email address and click accept.
Step 3 Check your emails - you should receive a message from Patchworks almost immediately, containing a link to complete the registration process. Click this link:
...the Patchworks registration page is displayed:
Step 4 Click the sign in with Google button:
Step 5 Select the Google account that you want to use - for example:
Step 6 Check confirmation details and click continue:
Step 7 When the first Patchworks registration page is displayed, confirm/change your name and click continue:
Step 8 Complete the second part of your registration (company details) - then click continue:
Step 9 Read and accept terms and conditions, then click the create Patchworks account button:
Step 10 You are directed back to the Patchworks login page, where you can log in with the sign in with Google button:
New companies have immediate access to a free trial which runs for 15 full days (ending at midnight on the 15th day).
Having registered from a Patchworks account, a company profile is added for the company that you registered. You'll need to access this profile to update company details or to view/manage users. Follow the steps below to access your company profile.
If you are an agency/partner with permissions to manage multiple companies, company profiles work a bit differently. Please refer to our Multi-company profiles section.
Step 1 Log into the Patchworks dashboard. and select settings from the bottom of the left-hand navigation bar.
Step 2 Select my company profile:
...the manage profile page is displayed with general details at the top, and extra information in the lower pane:
From here you can:
Update general details, including company name, website, telephone and email address
View users associated with this company profile
The steps detailed on this page show how to switch into a linked company that you manage and - when you've finished working with that company - how to switch back to your own company.
You can only switch into companies that you have been granted explicit permission to manage.
Your Patchworks account must have the manager role in order to view linked companies for your organisation.
Step 1 Click the arrow associated with your current company name and select the switch companies option:
If you don’t see this option it means that you don’t have not been granted access to manage any companies.
The managed companies page is shown, listing all companies that are linked to your organisation (i.e. all companies that can be managed by your team):
If you have been granted permission to manage a company, you'll see an icon in the switch column:
If your organisation manages a lot of companies this list might be long, running over multiple pages. If necessary, use the search field to quickly find a company by name.
Step 2 Click the ‘switch’ icon to the right of the required company profile:
If no icon is shown it means that you have not been granted access to manage this company.
Step 3 You are switched into this company profile:
Notice that the company name has changed at the top of your window - if you click the associated arrow, you'll find quick access to profile settings for this company, should you need to change general details or manage company users:
Any changes that you make from this point on will update the company you have switched into. Always ensure that you are switched to the right company before making changes.
Step 4 You can now proceed to complete any required setup for this company (for example, add and manage users, add connectors, process flows, etc.).
If required, you can copy process flows from one of your managed companies into another. For further information please see
Step 5 When you've finished working with this company, you should switch back to your own company to ensure that you don't make any subsequent updates in error.
When you've finished working with a managed company, follow the steps below to your own (i.e. original) company.
Step 1 Click the arrow associated with your current company name and select the switch companies option:
If you don’t see this option it means that you don’t have not been granted access to manage any companies.
Step 2 The managed companies page is shown.
Typically, no managed companies will be shown because you're currently switched into a managed company rather than your own profile.
Step 3 Click the switch to original company button:
Step 4 You are switched back to your own profile and the managed companies page updates to show all companies that your team can manage:
This is preview documentation for a feature that is scheduled for an upcoming release.
If your Patchworks account is associated with an admin role, you can add a message to be displayed as a dashboard banner. All users associated with your company profile will see this banner when they access the dashboard:
Message text is added and managed via your company profile page.
Only admin role users can add/manage message text.
Banner text persists until the message is removed from your company profile.
Step 1 Log into the Patchworks dashboard and access your company profile.
If you manage linked companies, make sure that you are switched into the company profile that you want to update.
Step 2 In the top general section, add required message text to the banner field:
Step 3 Save changes. Your banner is displayed immediately.
To amend the text displayed in a current banner, simply change the banner field text as needed and save changes. The banner updates as soon your updates are saved.
To remove a banner, clear all text from the banner field and save changes. The banner is cleared as soon as this change is saved.
Two-factor authentication (2FA) is a subset of multifactor authentication (MFA). It typically uses a one-time time-based passcode (TOTP) to add an extra layer of security to the user’s account.
Generally, 2FA works as follows:
A secure string of letters and numbers (known as a secret key) is generated.
This string is shared with an authenticator app on the user’s mobile device - usually by scanning a QR code.
The authenticator app uses the secret key, along with the current date/time to generate a code. These codes expire after a short period of time and a new one is generated.
When authenticating with an application, the user is prompted to retrieve the current code from their authenticator app and input it into the application. If the code matches what the application has generated, the user is authenticated.
When 2FA is enabled for your Patchworks account, you will log into the dashboard as normal with your username and password. Having entered your credentials, you are prompted to enter an authentication code, which you obtain from your authenticator app:
To enable 2FA for your Patchworks login, you will need an authenticator app - for example (but not limited to Google Authenticator, Microsoft Authenticator, Duo, Authy).
To enable 2FA for Patchworks, follow the steps below:
Step 1 Log into the Patchworks dashboard.
Step 2 Select settings (from the bottom of the left-hand navigation menu):
Step 3 Select my account settings:
Step 4 Select the multi-factor authentication tab:
Step 5 Click the enable button:
...setup information is displayed with a QR code:
Step 6 Open your preferred authenticator app and scan the QR code.
Step 7 Your authenticator app will generate a 2FA code, which you should enter in the Patchworks multi-factor authentication tab, then click confirm::
Step 8 A set of recovery codes is displayed, which can be used in the event that you can't access your authenticator app for any reason. Copy these codes somewhere secure (such as a password manager).
Step 9 Click the copied button to confirm that you've copied recovery codes - the setup is now complete:
The next time that you log into Patchworks, you'll be prompted to enter a 2FA code (generated by your authenticator app) before you can access the dashboard:
To disable 2FA for Patchworks, follow the steps below:
Step 1 Log into the Patchworks dashboard.
Step 2 Select settings (from the bottom of the left-hand navigation menu):
Step 3 Select my account settings:
Step 4 Select the multi-factor authentication tab:
Step 5 Click the disable MFA button:
Step 6 When prompted, confirm your decision:
There are two ways to access your company insights page:
The quickest way to access your company insights page is via the account summary link in the left-hand navigation bar:
Notice that you can also see a quick preview of your CPU and data usage for the current month:
Your company insights page can be accessed in settings - select the settings option (from the bottom of the left-hand navigation bar), then choose company insights:
If you need to 'un-link' a managed company from your profile, please contact your Patchworks Partner Manager.
Once a company has been removed from your profile, it's no longer shown in your - none of your team members will have access from this point forward.
However, any 'native' users associated with the company can continue to log into the Patchworks dashboard with their own credentials and manage their own company as required.
Adding & linking a new managed company for Patchworks partners and agencies.
If you are a Patchworks partner and you have the associated with your subscription, you can create new companies that are linked to your own profile. Having created a new linked company profile, you can go on to manage , , and .
Your is associated with an allowance for the number of companies that can be created in each subscription tier.
If you don't have the but require new linked companies to be added, please contact your Patchworks Partner Manager.
The steps to add a new, linked company profile are summarised below:
Step 1 Log into the Patchworks dashboard using your own Patchworks credentials and ensure that you are .
Step 2 In the top-left corner, click the arrow associated with your current company name and select the switch companies option:
Step 3 Click the create company button at the top of your managed companies page:
Step 4 Complete general details for this company:
Any email address provided here is used as the Patchworks point of contact for your company.
Step 5 Save the company profile to exit back to the mange companies list.
Step 6 Refresh/reload the browser page.
When details for your new company profile are saved, a new database is created behind the scenes. When you refresh your browser, options to work with the new company become available.
Step 7 Go the the next stage.
Step 1 Use the 'switch' icon associated with the new company, to switch into that profile - for example:
If you don't see the 'switch' option, reload the page again.
Step 2 In the top-left corner, click the arrow associated with the new company name and select the [[company]] profile option:
Step 3 Scroll down to the extra panel at the bottom of the company profile page, then select the [[company]] subscriptions tab:
...you'll see that the existing subscription is set to trial, by default:
Step 4 Use the core subscription tier dropdown field to select the required subscription for this company - for example:
All subscription tiers are listed but if you can only save a selection if your partner features allowance is not exceeded.
Step 5 Save the profile:
Having created a linked company and saved subscription details, you can go on to:
When you choose to you will see a managed companies list which shows all companies that are linked to your profile.
However, if your user account has not been granted explicit access to manage companies, the 'switch' option won't be available for you to use. In this case, you can access the managed companies list via Patchworks settings, as shown below.
The fact that a company is does not necessarily mean that you or anyone else in your team has the ability to manage it. Linked companies can only be managed by users in your team who have been .
Your Patchworks account must have the in order to view linked companies for your organisation.
Step 1 Log into the Patchworks dashboard using your own Patchworks credentials and ensure that you are .
Step 2 Click the settings option at the bottom of the left-hand navigation bar:
Step 3 Select the managed companies option:
Step 4 All linked companies for your organisation are shown:
You can download summary details for all of your linked companies via the managed companies page - for example:
Details for your own (managing) profile are also included.
The following details are provided for each of your linked companies:
Step 3 Click the download button:
Step 4 The CSV file is generated and saved to the default downloads folder for your browser.
Company insights can help you understand how your process flows are performing, and your resource usage.
With the ability to view details for all process flows that run in a given month, and drill down to the performance of individual shapes, this is a powerful tool to help you identify any areas that could be optimised to ensure maximum efficiency.
who can then and complete required tasks.
for the linked company who can then log in directly to access their own dashboard.
If you don't see this option it means that your user account does not have the required manager
role. In this case, .
If you have been granted permission to manage a linked company, you'll see an icon in the 'switch' column - you can use this to now. If no icon is shown it means that you have not been .
The fact that a company is does not necessarily mean that you or anyone else in your team has the ability to manage it. Linked companies can only be managed by users in your team who have been .
Your Patchworks account must have the in order to view linked companies for your organisation.
Step 1 Log into the Patchworks dashboard using your own Patchworks credentials and ensure that you are .
Step 2 Choose to for a list of all companies that you have permission to manage:
If you don't see this option it means that your user account does not have the required manager
role. In this case, .
id
The internal Patchworks id for the company.
Name
The company profile name.
Plans
This is typically only relevant for Patchworks admins for non-core systems.
Tiers
Current core subscription tier.
Parent
The name of the managing company (i.e. your own company profile)
Created at
The date & time the company profile was created.
Last login
The most recent date/time that someone logged into this company profile.
Score
The current company insights score.
Last flow run
The date & time of the last process flow run.
This section includes guidance for administrators to add and manage user accounts via your company profile. It also includes guidance for all users wishing to access and manage their own user details, together with general information about passwords, roles and permissions.
If you an an agency/partner who manages multiple companies via the Patchworks dashboard, please go to our Managing team members & users for linked companies section.
As a multi-company profile user with appropriate access to manage a linked company, you will encounter two different types of user when you switch into that company:
Native company users. These users are directly associated with the linked company. They can log into their Patchworks dashboard with their own credentials.
Team members with access. These users are directly associated with your company - they have (or can be given) permission to manage all aspects of a linked company.
The following criteria must be met for someone to access and manage linked company users. You must be:
A user associated with a multi-company profile AND
Your multi-company profile is associated with linked companies. AND
Your user account has a manager or administrator role. AND
You have been granted permission to manage the linked company in question.
If you meet this criteria then you can switch into a company that you manage and:
For information about managing company profiles for your linked companies, please see our Linked company profiles section.
In Patchworks, an operation is counted whenever a request is made to send or receive a payload to/from an endpoint.
Crucially, we're not concerned with the number of items in the payload - we simply count the number of times a process flow requests to send or receive a payload. This might happen in several ways:
Connector shape
A request is made (successfully or otherwise) to receive data from a specified endpoint.
Connector shape
A request is made (successfully or otherwise) to send data to a specified endpoint.
Webhook trigger
A webhook
is received (with or without a payload) in the first step of the process flow.
Event trigger
An event
is received (with or without a payload) in the first step of the process flow.
Patchworks API call
A Patchworks API call
is received (with or without a payload) in the first step of the process flow.
The number of payloads that a process flow sends or receives correlates to the number of operations logged. In the most straightforward case, you might create a process flow that always receives a single, unpaginated payload from one system and then sends a single, unpaginated payload to another system - this would be an operations count of 2.
However, as the complexity of process flows increases, so does the possibility that the number of payloads can increase during a process flow run. The most likely ways that this can happen are:
Paginated data. If you receive paginated data, you receive 1 payload for each page of data - so each page represents 1 receive operation. In short, an initial data pull can result in multiple receive operations. And if you receive multiple pages, it follows that multiple pages continue through the flow - which means (potentially) multiple pages will be sent into your destination system, resulting in multiple send operations.
Flow control. The flow control shape is typically used to batch an incoming payload into multiple, smaller payloads for onward processing. So, even if you start by receiving 1 payload, it's likely that you will be sending multiple payloads at the end of the flow.
The examples below show the impact that these scenarios can have on operation counts:
Existing users can access their company profile and view all associated user accounts. If you are a user with an administrator or manager role, you can also access options to create and manage user accounts.
If you are an agency/partner with permissions to manage multiple companies, company profiles work a bit differently. Please refer to our Managed company profiles section.
Follow the steps below to access the user list.
Step 1 Log into the Patchworks dashboard using your own Patchworks credentials.
Step 2 Log into the Patchworks dashboard, then select settings | my company profile to access your profile page - for example:
...your company profile page is displayed with general details at the top and additional information in an extra panel below:
Step 3 Move down to the extra panel, where the users tab is displayed by default and any existing users are shown.
The company insights page is designed to help you understand how your process flows are performing, and resource usage. At a glance you can see which process flows are most heavy on resources, drilling down to performance for connectors and shapes that are included within those process flows:
Company insights data is loaded at 1 a.m. every morning. This means that data for the current day will not be fully populated until 1 a.m. the following day.
There are five key areas to consider on the company insights page:
1
2
3
4
5
6
The snapshot panel provides summary metrics for the overall performance of your company's process flows, connectors used in process flows, and shapes used in process flows, for the selected month.
These metrics are summarised below:
Data usage
The aggregated size of all payloads that leave each shape in a process flow - these are known as payloads out.
Operation usage
Score
This is a measure of how efficient/expensive (in terms of processing) your process flows are, based on the amount of data processed per second - 999 is the highest score.
Your score is based on all runs for all process flows associated with your company profile. This includes flows that are:
Triggered by a schedule, webhook, or event
Initialised by an API request
Run manually
Enabled or disabled when run
Draft or deployed status when run
If your score is on the low side, it may be that your process flows are necessarily complex - including items such as scripts, transformations, flow control, caches, etc., will have an impact on your score.
The colour of usage gauges changes to reflect how close your usage is to the associated allowance.
The data usage value shown here is the same as displayed in the left-hand navigation bar. If you notice a difference occasionally, this is most likely due to caching - values in the navigation bar are cached but values on the main insights page are not. If this happens, you should work from values shown on the insights page (caching will resolve itself in due course).
You can view insights for process flows, connectors used in process flows, and shapes used in process flows (for the selected month) - click the required selector tab for whichever of these you want to view:
Changing the selection here updates all metrics and analysis for the new data type.
The combination chart shows aggregated CPU usage (line) and payload size (bars) by day, for the selected month:
You can interact with this chart in several ways:
Beneath the combination chart, you'll find a breakdown of items (process flows, connectors, or shapes) included in summary metrics.
When process flow data is selected, you'll see a list of process flows that have been run within the selected month:
For each entry you can see the process flow name, CPU time used, the number of times used (i.e. run); data usage, operations usage, and score. If your overall score is low, this is a great place to pinpoint particular process flows with a low score and may benefit from a review.
To view more details for an entry, click the associated 'view' icon - here you'll see a breakdown for each version of the process flow that has been run (in the selected month):
Depending on the length of process flow names, you may need to scroll horizontally to access this option.
When connector data is selected, you'll see a list of connectors that have been used within the selected month:
For each entry you can see the connector name, CPU time used, the number of times used; data usage, operations usage, and score. If your overall score is low, this is a great place to pinpoint particular connectors with a low score and may benefit from a review.
To view more details for an entry, click the associated 'view' icon - here you'll see a breakdown of the specific connector endpoints and instances that were used (in the selected month):
When shape data is selected, you'll see a list of shapes that have been used in process flows, within the selected month:
For each entry you can see the shape name, CPU time used, the number of times used; data usage, operation usage, and score. If your overall score is low, this is a great place to pinpoint a particular shape with a low score and may benefit from a review.
For script shapes, click the associated 'view' icon - here you'll see a breakdown for all scripts (and versions) that were used in the selected month:
If you manage multiple linked companies (using our partner features bolt-on), you can choose to view aggregated insights for all your managed companies:
After selecting this option, you'll see a snapshot panel with aggregated totals for your linked/managed companies.
If you want to see full company insights for a managed company, you should switch to that company and access company insights in the usual way.
If you are a user with an administrator or manager role, you can create new user accounts for your company profile. These users will be able to log into the dashboard for your company - the level of access that they have will depend on the role that you grant during the account creation process.
By default, new users are created with a user
role. Provided that you have an administrator
or manager
role, you can change this if required - the following rules apply:
Administrator
Can assign roles up to and including manager
level (e.g. change a user
account to a manager
account).
Can reduce other non-administrator accounts to a lesser role (e.g. change a user
account to a read-only
account).
Manager
Can assign roles up to and including user
level (e.g. change a read-only
account to a user
account).
Can reduce other non-manager accounts to a lesser role (e.g. change a user
account to a read-only
account).
For more information please see our Roles & permissions summary page.
If you are an agency/partner with permissions to manage multiple companies, company profiles work a bit differently. Please refer to our Managed company profiles section.
Step 1 Access the user list for your company profile.
Step 2 Move down to the extra section - you'll see a [company] users tab showing all existing user accounts. At a glance you can see each user's name, email address and role - for example:
Step 3 Click the create user button:
Step 4 Enter the person's name and email address:
The email address provided here is used to log into the Patchworks dashboard.
Step 5 Click the save button. The user account is saved and an email is sent to the given address, with a link for the user to set their password.
A password must be used with the user's email address in order to log into the Patchworks dashboard.
Step 6
The user roles tab is displayed and you'll see that the new account is created - by default, new accounts are created with a user
role:
If required, you can assign an alternative role by clicking the appropriate button.
Roles determine the level of access that users have in the Patchworks dashboard. See the table above for roles that you can set here.
Step 7 Save changes. Once the user has set their password (via the link provided in an email triggered in step 6) they can access the Patchworks dashboard for their own company.
Introduction
Data usage is calculated by aggregating the size of payloads that leave each shape in a process flow - these are known as payloads out.
In any process flow, data is received and passed from one shape to the next. Different shapes handle their incoming payload(s) in different ways - in some cases, data simply passes through (data in is the same as data out) but in others, data is manipulated and changed.
Understanding how these payloads are aggregated provides a clearer picture of your overall data usage.
A payload is the data generated/processed during the execution of any shapes within a flow. We refer to the payload out when it leaves that shape. This could be via any of the mechanisms below:
Patchworks API call
Data is received from or sent to an API call.
Connector shape
Data is received from or sent to a Patchworks connector.
Other shapes
Data is processed within any shape - for example, by a custom script (script shape or transform function), mapping payloads from one structure to another (map shape), or routing payloads down multiple branches (route shape).
File transfers
Data moves between systems - for example, CSV files or image files.
Database queries
Data is fetched from or inserted into a database.
Triggers
Data is sent/received via an event, webhook or Patchworks API call.
To calculate data usage, all payload out sizes (from each shape in a process flow) are aggregated. Here's how this works:
Typically, the size of a payload that goes into a process flow shape is the same as the payload out size - payloads are not modified unless your flow includes actions that are designed to do this.
The table below summarises process flow shapes and their ability to change the size of incoming payloads:
No
The payload out is always the same as the incoming payload.
No
The payload out is always the same as the incoming payload.
Yes
When receiving data, the payload out will reflect the volume of data received from this connection request.
When sending data, the payload out will be the same as the incoming payload UNLESS you choose to save response as payload
(in which case the payload out is - typically - smaller than the incoming payload).
No
If set to filter
or track & filter
, a de-dupe shape may reduce the size of the incoming payload by removing duplicate items.
If set to track
, the incoming payload simply passes through for tracking - the payload out will always be the same as the incoming payload.
A de-dupe shape will never increase the size of the payload out.
Yes
If a filter removes data from an incoming payload, the payload out will be smaller than the incoming payload. A filter will never increase the size of the payload out.
No
The incoming payload is batched into multiple, smaller batches but the aggregate size of the payload out for those batches is always equal to the incoming payload size.
Yes
The payload out will reflect the volume of data loaded from the cache.
Yes
No
The payload out is always the same as the incoming payload.
Yes
When an incoming payload hits a route shape, your defined conditions are checked and a payload out is created for each defined route.
If your route conditions exclude items in the incoming payload from progressing down any routes then the aggregate size of payloads out will be smaller than the incoming payload.
Yes
If you configure this shape with a manual payload then the payload out is likely to differ from any incoming payload. If no manual payload is specified then the payload out is always the same as the incoming payload.
Yes
A custom script might increase or decrease the size of the payload out.
No
The payload out is always the same as the incoming payload.
Yes
The incoming data is split at a defined data element, so only that element progresses to the next step - i.e. the payload out is likely to be smaller than the incoming payload.
No
The incoming payload simply passes through for tracking - the payload out will always be the same as the incoming payload.
A track data shape will never increase the size of the payload out.
The examples below show how data usage can be affected by different process flow shapes.
This page details roles and permissions for key areas of the Patchworks platform. User accounts can be associated with one of four possible roles:
Administrator
Manager
User
Read-only
The tables below summarise dashboard access by role. It's important to be aware that available features are determined by your core subscription tier. So, although a user's role might be associated with permissions to access a given feature, that feature is only available if it's included in the active subscription tier - think of it as 'tier trumps role'. For example:
All permissions refer to entities associated with your own company profile. If you manage multiple company profiles, please see our Multi-company profiles section for more information.
If you haven't upgraded to Core yet and are still using services to sync data, please check for roles & permissions information that's specific to services.
When someone registers for a Patchworks account, they are assigned to the administrator
role, automatically. This user can go on to create additional users and/or assign roles to other users as needed.
Typically, there is one administrator for each organisation. If you require more than one user with this role, please raise a support request.
The tables below summarise access by role for key tasks within the Patchworks dashboard:
Company permissions refer to features that are available from settings > my company profile.
View company profile
Update company profile name
Update company profile contact information
Add & manage banner messages
Delete company profile
Company user permissions refer to features that are available from settings > my company profile > extra > users.
View company users
Search company users
Create company user with an administrator
role
Create a company user with a manager
role
Create a company user with a user
or read-only
role
Update details for an existing company user (all roles)
Elevate an existing read-only
account to a user
role
Elevate an existing user
or read-only
account to a manager
role
Elevate an existing user
, read-only
or manager
account to an administrator
role
Reduce an existing manager
account to a user
or read-only
role
Reduce another administrator
account to a manager
, user
or read-only
role
Trigger password reset password for a company user
Update own user details
Elevate or reduce own role
Enable/disable own MFA
Delete company user
Delete own user profile
Company insights refers to your account summary company insights page.
View company insights
Permissions in this section are only relevant if you use Patchworks to manage multiple companies - i.e. you have a multi-company profile with one or more linked companies.
Adding & linking a new company to your multi-company profile
Switch in & out of linked companies
Update subscriptions for linked companies
View linked companies for your multi-company profile
Un-linking a company from your multi-company profile
View team members for own company
Create new team member to manage a linked company
Assign user roles for an existing team member
View team members who manage a linked company
Grant & revoke access for team members to manage a linked company
Trigger a password reset for an existing team member
Removing a team member account
View 'native' users for a linked company
Create a new 'native' user for a linked company
Assign user roles for an existing 'native' company user
Trigger a password reset for an existing 'native' company user
Remove a 'native' linked company user from their company profile
Marketplace permissions refer to features that are available from the marketplace page.
Install marketplace blueprints
Build blueprints
Browse & view marketplace connectors
Install marketplace connectors
Update marketplace connectors
Browse & view marketplace process flows
Install marketplace process flows
Browse marketplace scripts
Preview script from scripts list
Install marketplace scripts
Private marketplace permissions refer to features available to work with private marketplace resources.
View private marketplace
Install resources (blueprints, connectors, process flows, scripts, cross-reference lookups)
Upload resources (blueprints, connectors, process flows, scripts, cross-reference lookups)
Connector permissions refer to features that are available from the my connectors page.
Browse installed connectors
View installed connector settings
Update installed connector settings
Delete installed connectors
Connector instance permissions refer to features that are available from the my connectors page.
View connector instances
View connector instance settings
Update connector instance settings
Delete connector instances
Process flow permissions refer to features that are available from the process flows page.
View process flow list
View canvas content for existing process flows
Create process flows (add/update/remove shapes)
Update process flows (add/update/remove shapes)
Create cache (cache shape settings)
Create data pool (de-dupe shape settings)
Delete process flows
Run process flow manually
Enable & deploy process flows (process flow settings)
Apply/remove labels (process flow settings)
Create labels (process flow settings)
Apply/remove email failure groups (process flow settings)
Add flow variables (process flow settings)
Update flow variables (process flow settings)
Remove flow variables (process flow settings)
Duplicate process flow (process flow settings)
Run logs permissions refer to features that are available from the run logs page.
View run logs list
View run logs
View run logs (classic)
View run log details
Download run logs
View run log payloads
Download run log payloads
Stop process flow
General settings permissions refer to features that are available from the settings page.
Manage own account settings
View notification groups
Add & manage notification groups
View audit logs
Search audit logs
View labels
Add & manage labels
View data pools
Add & manage data pools
For my company profile permissions see company permissions and company users.
Custom script permissions refer to features that are available from the scripts page.
View custom scripts list
View custom script details
Create custom scripts
Update custom scripts
Delete custom scripts
Cross-reference lookup permissions refer to features that are available from the cross-reference lookups page.
View installed cross-reference lookups
Search installed cross-reference lookups
View cross-reference lookup values
Add & manage cross-reference values
Delete cross-reference lookups
Cache permissions refer to features that are available from the data caches page.
View existing cache lists
Search existing caches
View existing cache details
Update existing cache details
View existing cache contents
Clear existing cache contents
Delete caches
Obtain API token
Initialise process flow with payload
Having registered from a Patchworks account - or having been added to a company profile as a user - a user account is created for you. If required, you can access your account settings and:
To access your account settings, click your login name in the top, right-hand corner of the dashboard, then select the account settings option:
Step 1 Access your account settings page.
Step 2 Update information in the general panel as needed:
Remember that the email address specified here is used to log into the Patchworks dashboard.
Step 3 Click the save button.
If you want to enable/disable two-factor authentication for your account, move down to the extra panel and select the multi-factor authentication tab:
For more information please see our two-factor authentication (2FA) page.
Step 1 Click your login name in the top, right-hand corner of the dashboard, then select the change password option:
Step 2 Complete the change password form by entering your existing password, followed by the new password required and confirmation of this:
When setting your password, the following rules apply:
A minimum length of 8 characters
At least 1 lowercase letter (a - z)
At least 1 uppercase letter (A - Z)
At least 1 number (0 - 9)
At least 1 special character (!, $, #, or %)
Step 3 Click the submit button to save changes.
You may notice that there's a reset password option at the top of your account settings page. This option triggers a password reset email which includes a link to the password reset form shown above - so you achieve the same thing but with an extra step.
If you are a user with an administrator or manager role, you can trigger a password reset email for other users in your company.
When this is done, a reset email is sent to the email address for the user, containing a reset link. Password reset links are valid for 24 hours. After this, another password reset must be triggered so a new link is emailed.
Step 1 Access the user list for your company profile.
Step 2 Move down to the extra section - you'll see a [company] users tab showing all existing user accounts. At a glance you can see each user's name, email address and role - click the name of the user requiring a password reset:
Step 3 Click the reset password button at the top of the page:
Step 4 The user will receive an email from Patchworks which includes a link to change their password.
When a new user account is created, assigning them a role is part of the initial account creation process. If you are a user with an administrator or manager role, you can change the role(s) for an existing user account - the following rules apply:
Administrator
Can promote accounts to roles up to and including manager
level (e.g. change a user
account to a manager
account).
Can reduce other non-administrator accounts to a lesser role (e.g. change a manager
account to a user
account).
Manager
Can promote accounts to roles up to and including user
level (e.g. change a read-only
account to a user
account).
Can reduce other non-manager accounts to a lesser role (e.g. change a user
account to a read-only
account).
For more information please see our Roles & permissions summary page.
Step 1 Access the user list for your company profile.
Step 2 Move down to the extra section - you'll see a [company] users tab showing all existing user accounts. At a glance you can see each user's name, email address and role - click the name of the user that you want to update:
Step 3 Move down to the roles tab and assign (and/or remove) roles as needed using the appropriate assign role / remove role buttons:
The role associated with a user determines the level of access that they have within the Patchworks dashboard - for more information please see our Roles & permissions summary page.
Step 4 Save changes.
You can trigger a password reset email for another team member in your organisation, from your own company profile.
Step 1 that you want to update and .
Step 2 Click the name of the user that requires a password reset:
Step 3 Click the password reset option at the top of the page:
Step 4 This user will receive a Patchworks email containing instructions to reset their own password.
If your user account is associated with a , you can remove other team member accounts from your company profile.
When a team member is removed in this way, they can no longer log into the Patchworks dashboard. If you want to allow a team member to continue accessing the Patchworks dashboard for multi-company profile but need to prevent them from managing other companies, you can simply . In this way, the team member retains their dashboard access.
Step 1 .
Step 2 Click the name of the user account that you want to remove:
Step 3 Click the 'delete' icon at the top of the page:
Step 4 When prompted, confirm this removal.
Month selector. Choose a year and month to analyse - all subsequent data displayed is for the selected year/month:
. If you manage multiple linked companies (using our ), you'll see insights for your own (parent) company profile by default. You can also use this dropdown field to view aggregated insights for all your linked companies. This option is only displayed if the partner features bolt-on is enabled for your company profile.
. At a glance, view your aggregated resource usage and score. These numbers are for the month and currently selected.
. Choose the type of data be analysed - process flows, connectors, or shapes.
. A visual representation of CPU and data usage by day, for the month and currently selected.
. A breakdown of each process flow, connector, or shape (depending which data type is selected) that's included in aggregated totals for the selected month.
The total number of operations completed. For more information about how operations are calculated please see .
However, if a score is low, it's always worth as there may be places where your process flows can be optimised (for example, does a flow include lots of mapping transformations that could be achieved in a single script?).
By choosing to , it's sometimes very obvious which shapes are 'expensive' and making the biggest contribution to your lower score. However, if your score is on the low side and you're satisfied that the process flow is built optimally, don't worry too much about the score - it's just there as an indicator.
Please see our section for advice on building efficient process flows.
A straightforward like-for-like mapping between two systems will not affect the size of the payload out. However, if are applied the size of the payload out may change slightly - for example, prefix
, suffix
, format date
and script
transforms.
Typically, any size variations from mapping transformations are small.
If you would like to create an app and submit it for review to be added to the public app marketplace, we have outlined the following submission guide to ensure a high standard.
This document outlines the approval process for developers submitting blueprints for inclusion in the Patchworks marketplace. The Patchworks marketplace is a platform where users can discover, install, and use various pre-built blueprints to accelerate the onboarding process.
You must ensure that your blueprint meets the following requirements.
Compliance
The blueprint must comply with all relevant laws, regulations, and policies, including those related to data privacy, security, and intellectual property rights.
Functionality
The blueprint must provide clear and useful functionality that adds value for users. It should be well-designed, intuitive to use, and free from significant bugs or issues.
Quality
The blueprint must meet quality standards for performance, reliability, and user experience. It should not degrade the performance or stability of the Patchworks platform.
Security
The blueprint must implement appropriate security measures to protect user data and prevent unauthorised access or misuse. It should follow best practices for secure coding and data handling.
Marketplace compatibility
The blueprint should be compatible with the Patchworks platform and any relevant operating systems or devices. It should not rely on unsupported features or dependencies.
Connector compatibility
The blueprint should use existing connectors found in the Patchworks marketplace. Any modifications to existing connectors in order to support the blueprint must be submitted separately prior to the blueprint review process.
Documentation
You should provide clear and comprehensive documentation for your blueprint, including installation instructions, usage guidelines, and troubleshooting tips if any are required. Documentation can be provided as http links in multiple sections of the connector builder. Alternatively documentation can be submitted along with your blueprint. We will host this documentation on our public documentation platform.
The submission process for public blueprints consists of the following steps:
Before the development of the blueprint commences, you are encouraged to submit in writing (to your partner manager) the following details on any blueprint(s) you intend to create.
Developer name
The name and email address of your company or developer.
Patchworks company profile
The Patchworks dashboard company profile name under which you will create the new blueprint(s).
Blueprint name
The name of the blueprint to be displayed in the Patchworks marketplace.
Expected completion date
If known, provide the expected completion date for development.
Connectors
Specify the name of any connectors to be included in the new blueprint(s). If these connectors do not exist or require modifications, you must provide details about the required modifications.
Process flows
Provide information about any process flows that you intend to build utilising the specified connectors. This information should include the purpose of the process flow and any custom scripts that will be built.
Before submitting a blueprint for approval, you are encouraged to conduct a thorough review to ensure that your blueprint meets all requirements outlined above.
This includes testing for functionality, performance, and security.
Once the blueprint is ready, you can submit it via your account manager. The submission should include the following:
Documentation and user guides
Screenshots or demo videos
Contact information for the developer or support team
Once the blueprint and associated information are submitted, the Patchworks team will schedule a review meeting with the developers. During this meeting, you should be prepared to:
Go over the changes required for connectors, if any.
Review the proposed process flows and confirm their functionality.
Demonstrate working flows by showing data transmission between source and destination systems.
Review any scripts or custom components used in the blueprint.
After a blueprint is approved and listed in the Patchworks marketplace, you have certain responsibilities to maintain the app's quality and compliance.
Updates & maintenance
You should regularly update and maintain you blueprint(s) to ensure it remains compatible with the Patchworks platform and any relevant changes or updates.
Support
You must provide adequate support to users, including addressing enquiries, issues, and bug reports in a timely manner.
Compliance
You should continue to comply with all relevant laws, regulations, and policies, and promptly address any compliance issues that arise.
The approval process outlined above is designed to ensure that public blueprints included in the Patchworks marketplace meet our high standards for quality, functionality, and security. By following this process and meeting our submission requirements, you can contribute to a vibrant ecosystem of third-party blueprints that enhance the user experience on the Patchworks platform.
For further information or assistance with the blueprint submission process, please refer to the Patchworks support team.
Hover your cursor over an option to bring the corresponding data into focus:
Click an option to toggle the corresponding data on/off:
Hover your cursor over any data point to view summary information:
The Patchworks marketplace is your one-stop-shop for a range of pre-built resources that you can install to streamline your dashboard integrations:
Here you can browse and install:
To access the Patchworks marketplace, log into the Patchworks dashboard and select marketplace from the left-hand navigation menu:
If your user account is associated with appropriate permissions, you can also access your own private marketplace.
If you are a multi-company profile user with permission to manage another linked company, you can assign different user roles for existing 'native' user accounts associated with that company.
When you add a new company user account, assigning the required roles is part of the initial account creation process. Steps detailed on this page can be followed if you need to assign different roles for an existing team member.
If you are a multi-company profile user with an administrator
or manager
role, you can change the role associated with other lesser-role company users. The following rules apply:
Administrator
Can assign roles up to and including manager
level (e.g. change a user
account to a manager
account).
Can reduce other non-administrator accounts to a lesser role (e.g. change a user
account to a read-only
account).
Manager
Can assign roles up to and including user
level (e.g. change a read-only
account to a user
account).
Can reduce other non-manager accounts to a lesser role (e.g. change a user
account to a read-only
account).
For more information please see our Roles & permissions summary page.
Step 1 Access company users for the required linked company.
Step 2 Move down to the extra section and select the [company] users tab - here you will find all 'native' user accounts associated with this company - i.e. users who are directly associated with this company profile and can log into the Patchworks dashboard with their own credentials:
Step 3 Click the name of the user account that you want to update:
Step 4 The user roles tab is displayed and you'll see which roles are currently assigned for this account:
Step 5 Assign (and/or remove) roles as needed by clicking the appropriate assign role / remove role button.
If you attempt to assign a role that is outside of your own permissions, a failure message is displayed and the change will not be made.
Step 6 Save changes.
If you are a multi-company profile user with permission to manage another linked company, you can remove a 'native' user from their company profile.
When a company user is removed in this way, they can no longer log into the Patchworks dashboard.
Step 1 Access company users for the required linked company.
Step 2 Move down to the extra section and select the [company] users tab - here you will find all 'native' user accounts associated with this company - i.e. users who are directly associated with this company profile and can log into the Patchworks dashboard with their own credentials:
Step 3 Click the name of the user account that you want to remove:
Step 4 Click the 'delete' icon at the top of the page:
...and then confirm this action:
A Patchworks blueprint contains everything you need to perform a specific task - for example, to sync orders between Shopify and Virtualstock Supplier.
When you install a blueprint, all of its components (connectors, process flows, scripts, etc.) are installed and added to the relevant area of your Patchworks dashboard - connectors are added to your connectors page, process flows are added to your process flows list, custom scripts are added to your scripts list, etc.
From here you can complete the required setup (as documented for each blueprint) and get started!
For more information please see The anatomy of a blueprint.
Blueprints can be purchased from the Patchworks website. Having purchased a blueprint, it will be available to install from the blueprints tab in the marketplace:
Having purchased a blueprint from the Patchworks website, it becomes available in your dashboard marketplace within 24 hours.
Once a blueprint becomes available in your marketplace, you'll see it displayed as a tile which includes a visual summary of component parts - for example:
Here you can see which connectors are included in the blueprint, the blueprint title and creator, and a summary of contents. Summary icons are:
For a detailed view of what's included in a blueprint, click anywhere on the tile. This displays full details for the blueprint - from here, you can view all components and if required, you can choose to install the blueprint.
For more information, please see The anatomy of a blueprint.
For all information about working with blueprints, please see our blueprints section.
If you are a multi-company profile user with permission to manage another linked company, you can add a new 'native' user for that company.
Native users can log into the Patchworks dashboard to work with their own company profile, using their own login credentials. For more information about the different types of user associated with managed companies please see our managed company users introduction.
By default, new users are created with a user
role. If you are a multi-company profile user with an administrator
or manager
role, you can change this if required - the following rules apply:
Administrator
Can assign roles up to and including manager
level (e.g. change a user
account to a manager
account).
Can reduce other non-administrator accounts to a lesser role (e.g. change a user
account to a read-only
account).
Manager
Can assign roles up to and including user
level (e.g. change a read-only
account to a user
account).
Can reduce other non-manager accounts to a lesser role (e.g. change a user
account to a read-only
account).
For more information please see our Roles & permissions summary page.
Step 1 Access company users for the required linked company.
Step 2 Move down to the extra section and select the [company] users tab - here you will find all 'native' user accounts associated with this company - i.e. users who are directly associated with this company profile and can log into the Patchworks dashboard with their own credentials:
Step 3 Click the create user button:
Step 4 Enter the person's name and email address:
The email address provided here is used to log into the Patchworks dashboard.
Step 5 Click the save button. The user account is saved and an email is sent to the given address, with a link for the user to set their password.
A password must be used with the user's email address in order to log into the Patchworks dashboard.
Step 6
The user roles tab is displayed and you'll see that the new account is created - by default, new accounts are created with a user
role:
If required, you can assign an alternative role by clicking the appropriate button.
Step 7 Save changes. Once the user has set their password (via the link provided in an email triggered in step 5) they can access the Patchworks dashboard for their own company.
If you are a multi-company profile user with permission to manage another linked company, you can view all 'native' user accounts for that company - i.e. accounts for users at that company.
For more information about the different types of user associated with managed companies please see our managed company users introduction.
Step 1 Log into the Patchworks dashboard using your own Patchworks credentials.
Step 2 Switch into the managed company that you want to review.
Step 3 Click the arrow associated with the company name and select the [company] profile option - for example:
Step 4 Move down to the extra section and select the [company] users tab - here you will find all users who are directly associated with this company profile (and can log into the Patchworks dashboard with their own credentials):
From here you can click the name of a user to access their account profile and then update details, assign a different role, or trigger a password reset request.
When you install blueprints or process flows from the marketplace, the installation 'job' is added to a queue for completion. When the job is completed, a notification is added to your notification centre. The number of unread notifications is shown on the notification centre icon - from here you can view messages, navigate to associated resources (where applicable), or clear notifications.
The notifications icon is always available from the information bar at the top of the Patchworks dashboard, showing the number of unread notifications. Click this icon to view all pending notifications:
Some notifications are clickable and can be used to navigate directly to the installed resource. For example, clicking the link for a process flow navigates to that process flow in edit mode, so you can complete any post-installation setup steps required:
When you select a notification and navigate to the resource, that notification is cleared automatically.
To clear all notifications in the list, use the 'trash' icon at the very top - for example:
To clear a single notification, use the 'delete' icon associated with that entry - for example:
This document outlines the approval process for developers submitting public connectors for inclusion in the [Public Marketplace]. The [Public Marketplace] is a platform where users can discover, install, and use a range of pre-built connectors to accelerate the onboarding process. For in-depth guides on how to build a connector, please see our connector builder section. For a demonstration video of our connector builder, watch our CEO Jim Herbert build a connector in under 5 minutes:
If you are a developer seeking to submit a public connector for inclusion in the [Public Marketplace], you must ensure that their connector meets the following requirements.
Compliance
The connector must comply with all relevant laws, regulations, and policies, including those related to data privacy, security, and intellectual property rights.
Functionality
The connector must provide clear and useful functionality that adds value for users. It should be well-designed, intuitive to use, and free from significant bugs or issues.
Quality
The connector must meet quality standards for performance, reliability, and user experience. It should not degrade the performance or stability of the [Public Marketplace] platform.
Security
The connector must implement appropriate security measures to protect user data and prevent unauthorised access or misuse. It should follow best practices for secure coding and data handling.
Marketplace compatibility
The connector should be compatible with the [Public Marketplace] platform and any relevant operating systems or devices. It should not rely on unsupported features or dependencies.
Documentation (recommended)
Developers should provide clear and comprehensive documentation for their connector, including installation instructions, usage guidelines, and troubleshooting tips if any are required.
The submission process for public connectors consists of the following steps:
Before the development of the connector commences, you are encouraged to submit in writing (to your partner manager) the following details on any connector(s) you intend to create.
Developer name
The name and email address of your company or developer.
Patchworks company profile
The Patchworks dashboard company profile name under which you will create the new connector(s).
Connector name
The name of the connector to be displayed in the [Public Marketplace].
Expected completion date
If known, provide the expected completion date for development.
Before submitting a connector for approval, you are encouraged to conduct a thorough review of your connector to ensure it meets all requirements outlined above.
This includes testing the connector for functionality, performance, and security.
Once the connector is ready, you can submit it via your account manager. The submission should include the following:
Documentation and user guides (if required)
Screenshots or demo videos (if applicable)
Contact information for the developer or support team
Once the connector and associated information are submitted, the [Public Marketplace] team will schedule a review meeting with the developers. During this meeting, you should be prepared to:
Demonstrate working flows by showing data transmission between source and destination endpoints.
Review any scripts or custom components used in the connector authentication & endpoints.
After a connector is approved and listed in the [Public Marketplace], you have certain responsibilities to maintain the connector's quality and compliance.
Updates & maintenance
You should regularly update and maintain you connector(s) to ensure it remains compatible with the [Public Marketplace] platform and any relevant changes or updates.
Support
You must provide adequate support to users, including addressing enquiries, issues, and bug reports in a timely manner.
Compliance
You should continue to comply with all relevant laws, regulations, and policies, and promptly address any compliance issues that arise.
The approval process outlined above is designed to ensure that public connectors included in the [Public Marketplace] meet our high standards for quality, functionality, and security. By following this process and meeting our submission requirements, you can contribute to a vibrant ecosystem of third-party apps that enhance the user experience on the Patchworks platform.
For further information or assistance with the connector submission process, please refer to the [Public Marketplace] developer documentation or contact the [Public Marketplace] support team.
The process flows section of the marketplace allows you to browse and install a range of prebuilt process flows:
A prebuilt process flow includes all resources that are needed, including:
All connectors used in the process flow are installed without instances.
Having selected the process flows option from the marketplace, you can browse and install prebuilt process flows.
Process flows are displayed as tiles over a series of pages, which you can step through using page numbers at the bottom of the marketplace. Each process flow includes a visual summary of its component parts:
Here, the following details are shown for the process flow:
Name & description
The process flow name and description.
Date added to marketplace
The date that the process flow was uploaded to the marketplace.
Included connectors
Logos for connectors included in the process flow - i.e. connectors to be installed if you choose to install this process flow.
Created
The name of the company that created this process flow.
To see a read-only view of a process flow before it's installed, click the view button:
Here you can see the process flow, with a breakdown of its components:
To install a process flow, click the install button:
The process flow is queued for installation and can be found in your own process flows list soon after.
Depending on the process flow and your existing setup, you may need to add instances for newly installed connectors and confirm endpoint details for connection shapes. For more information please see Installing a prebuilt process flow.
For all information about working with process flows (including how to build your own), please see our Process flows section.
If you manage , it can be useful to share resources between them. With appropriate user , you can access a private marketplace for your company profile. Any , , , or that you build can be uploaded to your private marketplace to be viewed/installed by:
Users associated with your own company profile
Users associated with any that you manage
To upload resources to your private marketplace, your user account must be associated with an administrator role.
To install resources from your private marketplace, user accounts must be associated with a manager role or above.
You can bundle resources into a blueprint and . A blueprint can include Patchworks connectors, custom connectors, process flows, scripts, cross-reference lookups, caches and data pools.
You can , , , and to your private marketplace.
To upload a process flow (or bundle a process flow in a blueprint), it must be deployed.
To upload a script (or bundle a script in a blueprint), it must be saved and deployed.
If you are a parent company administrator managing multiple linked profiles, you might upload resources to your own private marketplace and/or the private marketplace for any child company.
With this in mind, it's important to understand how resource visibility works in a parent/child company context. This is shown in the table below:
Having , , and a process flow, you can upload it to the process flows section of your private marketplace. This guide walks through the steps needed to achieve this.
You only need to upload a process flow to your private marketplace if you want to make it available for your users (and your linked company users) to download as a standalone resource. If you just want to include the process flow in a blueprint, you don't need to upload it separately - please see .
When you upload a process flow, any configured connectors, scripts, cross-reference lookups, caches and de-dupe pools will be included.
Ensure that the process flow you want to upload is and .
Step 1 Login to the Patchworks dashboard and ensure you're switched to the correct company profile.
Any resources you upload to the private marketplace for your own 'parent' company will be available to your 'child' companies (via their private marketplaces). Similarly, any resources uploaded to the private marketplace for a 'child' company will be available to the 'parent' company AND all child-sibling companies. For more information please see .
Step 2 From the left-hand navigation menu, select process flows | process flows options - all of your process flows are listed.
Step 3 Click the name of the process flow that you want to upload - the process flow is displayed.
Step 4 Click the settings option from the actions bar:
Move down to the versions panel and ensure that the deployed version is displayed - check that this is the version that you want to upload.
If you don't want to use the version that's currently deployed, you should edit the draft and deploy this.
Step 5 Click the ellipses associated with the deployed version and select the upload to marketplace option:
Step 6 Click the upload button to upload this process flow to your private marketplace. The upload is queued for processing and will be completed as soon as possible.
Your private marketplace can be accessed via the main Patchworks marketplace - it's simply a case of toggling between 'public' and 'private'.
Step 1 Log into the dashboard and (if you're managing multiple company profiles) ensure that you've .
Step 2 Select a tab to view: , , , , or .
Step 3 Click the private tab to the right of the tabs:
Any resources that have been uploaded by users associated with your company profile or (for linked companies) your parent company profile are displayed - for example:
Having , you can upload it to the scripts section of your private marketplace. This guide walks through the steps needed to achieve this.
You only need to upload a script to your private marketplace if you want to make it available for your users (and your linked company users) to download as a standalone resource.
If you just want to include the script in a process flow or an app, you don't need to upload it separately - please see or .
Ensure that the script that you want to upload is
Step 1 Login to the Patchworks dashboard and ensure you're switched to the correct company profile.
Any resources you upload to the private marketplace for your own 'parent' company will be available to your 'child' companies (via their private marketplaces). Similarly, any resources uploaded to the private marketplace for a 'child' company will be available to the 'parent' company AND all child-sibling companies. For more information please see .
Step 2 From the left-hand navigation menu, select process flows | scripts options - all of your custom scripts are listed.
Step 3 Find the script that you want to upload - it should have a deployed status:
Step 4 Click the name of the script to access script details, then click the upload button:
Step 5 The upload is queued for processing and will be completed as soon as possible.
The number of included .
The number of included .
The number of included .
The number of included .
If you install an process flow which includes a connector that you have already installed from the , a fresh copy of that connector is added alongside the existing one. You can then decide which one to use.
All scripts defined in are installed and deployed, ready for use.
All cross-reference lookups defined as are installed and ready for use.
Any data pools defined in are added. These are 'clean' data pools (i.e. with no associated data), ready for use.
Any caches and cache keys defined in are added. These are 'clean' caches (i.e. with no associated data), ready for use.
The number of included in this process flow - i.e. connectors to be installed if you choose to install this process flow.
The number of included in this process flow - i.e. scripts to be installed if you choose to install this process flow.
The number of steps in the process flow - i.e. the number of after the initial .
The number of included in this process flow - i.e. cross-reference lookups to be installed if you choose to install this process flow.
Indicates whether or not the process flow includes advanced shapes. Advanced shapes are: , , . Read and write access to advanced shapes is determined by your .
You'll only see this option for a deployed process flow. If you are checking a deployed version and this option isn't shown, it's likely that your user account does not have the required permissions. Please if this is the case.
Check your for confirmation if you miss the popup message when this is done.
You'll only see this option for a deployed script. If you are checking a deployed version and this option isn't shown, it's likely that your user account does not have the required permissions. Please if this is the case.
Check your for confirmation if you miss the popup message when this is done.
Parent marketplace
Child marketplace
This section contains quick, task-based guidance for queries that may arise when working with the Patchworks marketplace.
Having purchased a blueprint from the Patchworks website, it is added to your company profile and can be installed via the Patchworks marketplace in your dashboard.
Blueprints are added to your dashboard marketplace within 24 hours of purchase.
Once installed, all blueprint components (connectors, process flows, scripts, etc.) are added to the relevant area of your Patchworks dashboard - connectors are added to your connectors page, process flows are added to your process flows list, custom scripts are added to your scripts list, etc.
After installation, some setup is required before you put your installed process flows live. This setup varies for each blueprint and you'll find a specific installation guide for each.
If you install a blueprint which includes a connector that you've already installed from the connector marketplace, a fresh copy of that connector is installed alongside the existing one. You can then decide which one to use.
As part of the blueprint installation process, you can add instances for included connectors - this is where you provide your authentication credentials for the associated third-party system. If you have the required credentials to hand, we recommend adding them here.
When a blueprint is installed, its process flows are disabled and set to a draft status. When you are ready, you should enable and deploy any process flows that you want to use. Keep in mind that your Patchworks subscription tier determines the number of process flows and connectors that you can deploy.
If your user account is associated with an administrator role, you can build your own blueprints and upload them to your private marketplace.
If you'd like to make your blueprint available in the Patchworks public marketplace, you should submit it for approval.
This section provides a technical overview of process flows that are included with the Shopify & Virtualstock Supplier blueprint.
This page details Patchworks IPs that should be whitelisted if required (typically if you are experiencing connection issues and your systems are behind a firewall).
Patchworks NordLayer VPN
89.47.62.54
AWS Production K8s Cluster
18.168.241.46
18.168.94.149
13.41.170.82
If your team needs to manage multiple companies and each of these companies has its own Patchworks dashboard and its own setup, how do you manage these efficiently?
This is achieved by adding required 'child' companies and then linking these to your own profile. When this is done, yours becomes a multi-company profile and your team members (with an appropriate Patchworks role) can be granted access to manage linked companies. This allows them to 'switch into' a company that they manage and perform required tasks.
Having 'switched into' a company, you can do everything that a user directly associated with that company can do - for example, manage users, install connectors, build process flows, etc.).
Having added all resources that you want to include in a blueprint (custom connectors, process flows, scripts, and cross-reference lookups) you can create a blueprint and upload it to your private marketplace. This guide walks through the steps needed to achieve this.
Creating and uploading a blueprint requires you to select existing resources that you want to include. As such, all required resources (custom connectors, process flows, scripts, and cross-reference lookups) must be created and ready to use within your own multi-company profile - i.e.:
Any custom connectors must be created
Any Patchworks prebuilt connectors must be installed
Any process flows must be created, enabled, and deployed
Any scripts must be saved and deployed
Any cross-reference lookups must be installed/created
If you manage multiple companies, it's important to ensure that you're switched to your own company profile before creating required blueprints (and associated resources). For more information please see our private marketplaces page.
Having created/installed/deployed all resources that you want to bundle as a blueprint, follow the steps below to build and upload your blueprint.
Step 1 Login to the Patchworks dashboard and ensure you're switched to the correct company profile.
Any resources you upload to the private marketplace for your own 'parent' company will be available to your 'child' companies (via their private marketplaces). Similarly, any resources uploaded to the private marketplace for a 'child' company will be available to the 'parent' company AND all child-sibling companies. For more information please see About private marketplace access.
Step 2 Select the marketplace option from the left-hand navigation menu, then select the blueprint tab.
Step 3 Click the build new blueprint option:
If you don't see this option, it's likely that your user account does not have the required permissions. Please contact Patchworks support if this is the case.
...now you can use the create a blueprint form to select all resources that you want to include in this blueprint:
Step 4 First, enter a name for this blueprint (this name is displayed for users to see in your private marketplace) and - if available - a link for any existing help documentation.
Step 5 Use the process flows dropdown list to select any process flows that you want to include:
Here you'll see all process flows that have been created within the current company profile, which are deployed.
Step 6 By default, any connectors found in previously selected process flows (via connector shapes) will be selected for inclusion in this blueprint. If required, you can use the select connectors field to choose additional connectors to be included:
The select connectors list will show all connectors that you have installed or built, which are NOT already selected.
Step 7 By default, any cross-reference lookups found in previously selected process flows (via map shape transformations) will be selected for inclusion in this blueprint. If required, you can use the select cross-reference lookups field to choose additional lookups to be included:
The select cross-reference lookups list will show all lookups that you have installed or created, which are NOT already selected.
Step 8 By default, any caches found in previously selected process flows (via add to cache and load from cache shapes) will be selected for inclusion in this blueprint. If required, you can use the select caches field to choose additional caches to be included:
The select caches list will show all caches that you have created, which are NOT already selected.
Step 9 By default, any data pools found in previously selected process flows (via the de-dupe shape) will be selected for inclusion in this blueprint. If required, you can use the select data pools field to choose additional data pools to be included:
Step 9 Click the upload button to upload this blueprint to your private marketplace:
The upload is queued for processing and will be completed as soon as possible.
Check your notification centre for confirmation if you miss the popup message when this is done.
You've installed a process flow from the Patchworks marketplace via a blueprint or via the process flows section. When you run the process flow it either fails or does not work as expected.
When a blueprint or a process flow is installed, it usually includes dependencies such as connectors, scripts, caches, etc. If a dependency fails to install or has not been deployed correctly, this can cause associated process flows to fail or give unexpected results.
Check the following:
Once a blueprint or process flow has been installed from the marketplace, a series of confirmation messages is displayed - one message for each component.
Typically these are 'success' messages, but occasionally you may see a failure for one or more components. These messages are displayed briefly and then cleared however, you can review them later from your notifications centre.
If any part of the installation is shown to have failed, you can install the blueprint or process flow again.
When installing a blueprint you have the option to exclude given process flows. If you've already been working on process flows that you installed originally and don't want to lose these changes, you should exclude them before running the install again.
Installation instructions for Patchworks blueprints and process flows include some post-install setup steps - these must be completed before any associated process flows will run correctly. Double-check these steps to ensure that all required setup has been completed:
Any custom scripts associated with a Patchworks blueprint or process flow are installed and deployed as part of the installation process. However, if an installed process flow is not working as expected, it's a good idea to check that all required scripts are deployed. To do this, follow the steps below.
Step 1 Select scripts from the left-hand navigation menu:
Step 2 Check the deployment status column for listed scripts - you're looking for any that show as un-deployed:
Step 3 Click the name of the first un-deployed script:
Step 4 Scroll down and click the save and deploy button:
Step 5 Repeat these steps for any other scripts that need to be deployed.
A Patchworks blueprint contains everything you need to perform a specific task - for example, to sync orders between Shopify and Virtualstock Supplier.
You can browse and purchase blueprints from the Patchworks website. Having purchased a blueprint, it is added to your company profile and becomes available in the blueprints section of the Patchworks marketplace:
Having purchased a blueprint from the Patchworks website, it becomes available in your dashboard marketplace within 24 hours.
Suppose you need to change any component within a blueprint that's in your private marketplace (i.e. a blueprint that has been uploaded to your private marketplace and is available from the blueprints tab). In this case, you need to follow the steps below.
Step 1 Make changes to connectors, process flows, scripts, or cross-reference lookups, as needed.
Step 2 Delete the existing blueprint from your private marketplace.
Step 3 Upload a new blueprint with updated resources.
Uploading a new blueprint does not update any existing installations. If a private marketplace blueprint has been installed (either in your company profile or for a linked company profile) you will need to switch to the relevant company profile and make any required changes to installed resources.
Suppose you need to change a custom connector that's in your private marketplace (i.e. a connector that has been uploaded to your private marketplace and is available from the connectors tab). In this case, you can make the required changes and then re-upload the connector - the steps for this are:
Step 1 Select process flows | connectors & instances from the left-hand navigation menu to view your installed/custom-built connectors.
Step 2 Find the connector that you want to update and make changes to the connector settings as needed:
Step 3 When any changes are saved for a connector that has already been uploaded to the marketplace, a re-upload button becomes available:
Step 4 If this connector is in use for any of your linked ('child') companies, you'll see an update available option when viewing connectors in that company profile - for example:
...use this to install your updates.
If you need to change a process flow, script, or cross-reference lookup that's in your private marketplace, follow the steps below.
Step 1 Make the required changes to the resource.
If you change a process flow, ensure the required version is enabled and deployed.
If you change a script, ensure it's saved and deployed.
Step 2 Delete the existing resource from your private marketplace.
Step 3 Upload the updated resource.
Uploading a new resource does not update any existing installations. If a private marketplace resource has been installed (either in your company profile or for a linked company profile) you will need to switch to the relevant company profile and make any required changes there.
Having built a custom connector (or edited a Patchworks connector to work in a different way), you can upload it to the connectors section of your private marketplace. This guide walks through the steps needed to achieve this.
You only need to upload a custom connector to your private marketplace if you want to make it available for your users (and your linked company users) to download as a standalone resource. If you just want to include the connector in a process flow or a blueprint, you don't need to upload it separately - please see Uploading process flows to your private marketplace or Uploading blueprints to your private marketplace.
Step 1 Login to the Patchworks dashboard and ensure you're switched to the correct company profile.
Any resources you upload to the private marketplace for your own 'parent' company will be available to your 'child' companies (via their private marketplaces). Similarly, any resources uploaded to the private marketplace for a 'child' company will be available to the 'parent' company AND all child-sibling companies. For more information please see About private marketplace access.
Step 2 From the left-hand navigation menu, select process flows | connectors options - all of your installed/custom connectors are listed.
Step 3 Find the connector that you want to upload - it should be displayed with the name of your company profile (rather than Patchworks) and an upload option:
Step 4 Click the upload option.
If you don't see an upload option, it's likely that your user account does not have the required permissions. Please contact Patchworks support if this is the case.
Step 5 The upload is queued for processing and will be completed as soon as possible. Check your notification centre for confirmation if you miss the popup message when this is done:
Check your notification centre for confirmation if you miss the popup message when this is done.
The Shopify & Descartes Peoplevox blueprint includes everything you need to:
Sync products from Shopify to Peoplevox
Sync orders from Shopify to Peoplevox
Sync stock from Peoplevox events to Shopify
Sync refunds (using returns report data) from Peoplevox to Shopify
Sync fulfilments from Peoplevox events to Shopify
Subscribe to Peoplevox fulfilment post events
Subscribe to Peoplevox stock events (using site filters)
Unsubscribe from Peoplevox events
Process flows are built to implement powerful data flows between connector instances in an intuitive, visual way - this is where we define if, when, what, and how data is synced. All process flows installed with this blueprint are shown below.
You'll find installed process flows in the manage process flows area of your dashboard. For product documentation please see Process flows.
A connector is a generic integration of a third-party business system/application. Connector instances (configured by you as part of the blueprint install process, or later via your connectors page), are added to process flows via the connector shape. All connectors installed with this blueprint are shown below.
You'll find installed connectors in the manage connectors area of your dashboard. For product documentation please see Connectors & instances.
Custom scripts are implemented via the script shape, and are typically used when source data needs to be manipulated beyond the capabilities that standard transform functions provide. All scripts installed with this blueprint are shown below.
Format to PVX Data
Format json to Peoplevox data.
Strip Data Array
Strips data array for graphQL request.
Format PVX Event Fulfilment Data
Formats event fulfilment data to line items array.
Set PVX Time Filter
Sets a time filter variable in Peoplevox format.
PVX XML to JSON
Formats Peoplevox data into json.
PVX Returns Combine Report Data Lines
Combines report data by sales order number.
Calculate Shopify Refunds
Calculates refunds from suggested refund data.
Flatten Products
Flattens products to one list of variants.
Generate Sku Query
Generates a Shopify GraphQL query for provided SKUs.
Calculate Inventory Adjust
Calculates inventoryItemAdjustments.
Combine Fulfilment Lines
Combines report data by sales order number.
You'll find installed scripts in the scripts area of your dashboard. For product documentation please see Custom scripting.
Cross-reference lookups are used for cases where some values are commonly known by other terms. If source data includes values that always need to be changed to an alternative term, a cross-reference lookup can be used to transform required data fields (via the map shape). All cross-reference lookups installed with this blueprint are shown below.
N/A
This app does not include any cross-reference lookups.
You'll find installed cross-reference lookups in the cross-reference lookups area of your dashboard. For product documentation please see Cross-reference lookups.
Caches are specified in the add to cache shape, and used to store data (temporarily) at given points in a process flow. Typically, this is done so the data at that point in time can be referenced later in the same process flow, or by other process flows, via a load from cache shape. All caches installed with this blueprint are shown below.
Stock Event Data
Flow run
Original Return Data
Flow run
Original Fulfilment Data
Flow run
Fulfilment Order Line ID
Flow run
Order Data
Flow run
You'll find installed caches in the data caches area of your dashboard. For product documentation please see Cache shapes.
Data pools are used by the de-dupe shape in process flows. They store unique key field values that have passed through the shape, so subsequent records can be checked and matched for duplication. All data pools installed with this blueprint are shown below.
Returns ID
return code
The Shopify & NetSuite blueprint includes everything you need to sync customer details and orders from Shopify to NetSuite.
Process flows are built to implement powerful data flows between connector instances in an intuitive, visual way - this is where we define if, when, what, and how data is synced. All process flows installed with this blueprint are shown below.
You'll find installed process flows in the manage process flows area of your dashboard. For product documentation please see Process flows.
A connector is a generic integration of a third-party business system/application. Connector instances (configured by you as part of the blueprint install process, or later via your connectors page), are added to process flows via the connector shape. All connectors installed with this blueprint are shown below.
You'll find installed connectors in the manage connectors area of your dashboard. For product documentation please see Connectors & instances.
Custom scripts are implemented via the script shape, and are typically used when source data needs to be manipulated beyond the capabilities that standard transform functions provide. All scripts installed with this blueprint are shown below.
-
-
You'll find installed scripts in the scripts area of your dashboard. For product documentation please see Custom scripting.
Cross-reference lookups are used for cases where some values are commonly known by other terms. If source data includes values that always need to be changed to an alternative term, a cross-reference lookup can be used to transform required data fields (via the map shape). All cross-reference lookups installed with this blueprint are shown below.
-
-
You'll find installed cross-reference lookups in the cross-reference lookups area of your dashboard. For product documentation please see Cross-reference lookups.
Caches are specified in the add to cache shape, and used to store data (temporarily) at given points in a process flow. Typically, this is done so the data at that point in time can be referenced later in the same process flow, or by other process flows, via a load from cache shape. All caches installed with this blueprint are shown below.
Orders
Flow run
You'll find installed caches in the data caches area of your dashboard. For product documentation please see Cache shapes.
Data pools are used by the de-dupe shape in process flows. They store unique key field values that have passed through the shape so subsequent records can be checked and matched for duplication. All data pools installed with this blueprint are shown below.
-
-
-
The Lightspeed X-Series & Shopify blueprint includes everything you need to sync:
Stock data from Shopify to Lightspeed X-Series
Product data from Shopify to Lightspeed X-Series
Sales order data from Lightspeed X-Series to Shopify
Customer data from Lightspeed X-Series to Shopify
Process flows are built to implement powerful data flows between connector instances in an intuitive, visual way - this is where we define if, when, what, and how data is synced. All process flows installed with this blueprint are shown below.
You'll find installed process flows in the manage process flows area of your dashboard. For product documentation please see Process flows.
A connector is a generic integration of a third-party business system/application. Connector instances (configured by you as part of the blueprint install process, or later via your connectors page), are added to process flows via the connector shape. All connectors installed with this blueprint are shown below.
You'll find installed connectors in the manage connectors area of your dashboard. For product documentation please see Connectors & instances.
Custom scripts are implemented via the script shape, and are typically used when source data needs to be manipulated beyond the capabilities that standard transform functions provide. All scripts installed with this blueprint are shown below.
Check if customer exists in Shopify
Checks if customers already exist in Shopify.
Convert Order ID to Metadata
Converts order id
to metadata.
Set Inventory ID
Sets inventory ID
to metadata.
Set Product ID
Sets product ID
to metadata.
Set Shopify Customer ID
Sets customer ID
to metadata.
You'll find installed scripts in the scripts area of your dashboard. For product documentation please see Custom scripting.
Cross-reference lookups are used for cases where some values are commonly known by other terms. If source data includes values that always need to be changed to an alternative term, a cross-reference lookup can be used to transform required data fields (via the map shape). All cross-reference lookups installed with this blueprint are shown below.
-
-
You'll find installed cross-reference lookups in the cross-reference lookups area of your dashboard. For product documentation please see Cross-reference lookups.
Caches are specified in the add to cache shape and used to store data (temporarily) at given points in a process flow. This means that data from a previous point in time can be referenced later in the same process flow or by other process flows, via a load from cache shape. All caches installed with this blueprint are shown below.
Sales Cache
Flow run
Stock Cache
Flow run
You'll find installed caches in the data caches area of your dashboard. For product documentation please see Cache shapes.
Data pools are used by the de-dupe shape in process flows. They store unique key field values that have passed through the shape so subsequent records can be checked and matched for duplication. All data pools installed with this blueprint are shown below.
Lightspeed Customers
customer email
The SEKO Logistics & Shopify blueprint includes everything you need to sync:
Inventory data from SEKO to Shopify
Fulfillments from SEKO to Shopify
Sales orders from Shopify to SEKO web sales orders
Process flows are built to implement powerful data flows between connector instances in an intuitive, visual way - this is where we define if, when, what, and how data is synced. All process flows installed with this blueprint are shown below.
You'll find installed process flows in the manage process flows area of your dashboard. For product documentation please see Process flows.
A connector is a generic integration of a third-party business system/application. Connector instances (configured by you as part of the blueprint install process, or later via your connectors page), are added to process flows via the connector shape. All connectors installed with this blueprint are shown below.
You'll find installed connectors in the manage connectors area of your dashboard. For product documentation please see Connectors & instances.
Custom scripts are implemented via the script shape, and are typically used when source data needs to be manipulated beyond the capabilities that standard transform functions provide. All scripts installed with this blueprint are shown below.
Add lineNumber to SalesOrderLineItem and Remove zero qty lines
Add lineNumber
to SalesOrderLineItem
and remove zero quantity lines.
SKU Search Script
Extracts and formats product codes.
GQL Set Onhand Inv Level
Set the Onhand
inventory level input to Shopify GQL.
Add SetQuantities to Stock Update GQL
Add SetQuantities
to stock update GQL
You'll find installed scripts in the scripts area of your dashboard. For product documentation please see Custom scripting.
Cross-reference lookups are used for cases where some values are commonly known by other terms. If source data includes values that always need to be changed to an alternative term, a cross-reference lookup can be used to transform required data fields (via the map shape). All cross-reference lookups installed with this blueprint are shown below.
-
-
You'll find installed cross-reference lookups in the cross-reference lookups area of your dashboard. For product documentation please see Cross-reference lookups.
Caches are specified in the add to cache shape, and used to store data (temporarily) at given points in a process flow. Typically, this is done so the data at that point in time can be referenced later in the same process flow, or by other process flows, via a load from cache shape. All caches installed with this blueprint are shown below.
AvailableStock
Flow run
FulfillmentOrder
Flow run
FulfillmentOrderMulti
Flow run
You'll find installed caches in the data caches area of your dashboard. For product documentation please see Cache shapes.
Data pools are used by the de-dupe shape in process flows. They store unique key field values that have passed through the shape so subsequent records can be checked and matched for duplication. All data pools installed with this blueprint are shown below.
-
-
-
Sales orders are pulled from Virtualstock Supplier and created in Shopify with a paid
and unfulfilled
status. Finally, an acknowledgement is sent back to Virtualstock Supplier.
Any orders with an ORDER
status are pulled from Virtualstock Supplier. Once an order is successfully sent into Shopify, we send an ORDER_ACK
back to Virtualstock Supplier - the order is then moved into ORDER_ACK
status so that it won't be picked up in subsequent flow runs.
The operations count for this process flow is: 4 per order.
For reference, all shapes in this process flow are documented below. Do not change shape settings unless advised to do so in our installation guide.
Trigger
Connector
If instance credentials are provided as part of the blueprint installation, there should be no need to change any settings for this shape. For reference, the required settings are:
Source instance
: Virtualstock Supplier
Source endpoint
: GET List orders
Variables
: Set as Status
/ ORDER
Flow control
There should be no need to change any settings for this shape. For reference, required settings are:
Source instance
: Virtualstock Supplier
Source endpoint
: GET List orders
Batch level
: *
Batch size
: 1
Map
Add to cache
These settings should not be changed. For reference, required settings are:
Cache
: (Flow run) VSSalesOrder
Cache key
: VSSalesOrder
Append
: OFF
Save all pages
: OFF
Script
These settings should not be changed. For reference, required settings are:
Script
: SKU Search Script
Version
: v3 (latest)
Connector
If instance credentials are provided as part of the blueprint installation, there should be no need to change any settings for this shape. For reference, the required settings are:
Source instance
: Shopify
Source endpoint
: POST Get VariantID by SKU - GraphQL
Variables
: Set as Query String
/ [[payload.productCodeString]]
Add to cache
These settings should not be changed. For reference, required settings are:
Cache
: (Flow run) VSSalesOrder
Cache key
: VSSalesOrder
Append
: ON
Path to append to
: SKUData
Save all pages
: OFF
Load from cache
These settings should not be changed. For reference, required settings are:
Cache
: (Flow run) VSSalesOrder
Cache key
: VSSalesOrder
Fail on cache miss
: OFF
Load all pages
: OFF
Script
These settings should not be changed. For reference, required settings are:
Script
: Match Shopify Variant to SKU
Version
: v3 (latest)
Connector
If instance credentials are provided as part of the blueprint installation, there should be no need to change any settings for this shape. For reference, the required settings are:
Source instance
: Shopify
Source endpoint
: POST Create an order
Route
If instance credentials are provided as part of the blueprint installation, there should be no need to change any settings for this shape. For reference, the required settings are:
Source instance
: Virtualstock Supplier
Source endpoint
: N/A
Routing method
: Follow all matching routes
Route 1
: No Errors
Route 2
: Error
Route 1
Payload fields
: order.id
Type
: Null comparison
Operator
: Not NULL
Keep matching
: ON
Route 2
Payload fields
order.id
Type
: Null comparison
Operator
: Is NULL
Keep matching
: ON
(Route 1) Script
These settings should not be changed. For reference, required settings are:
Script
: Save Order URI ID to Meta Var
Version
: v6 (latest)
(Route 1) Map
(Route 1) Connector
If instance credentials are provided as part of the blueprint installation, there should be no need to change any settings for this shape. For reference, the required settings are:
Source instance
: Virtualstock Supplier
Source endpoint
: POST Acknowledge an order
Variables
: Set as Order URI
/ [[meta.VSorderId]]
(Route 2) Connector
These settings should not be changed. For reference, required settings are:
Expected Payload
: Order failed to create if reached here.
Phone Number Formatter
Corrects formatting for UK telephone numbers.
SKU Search Script
Creates GraphQL input for Shopify.
Match Shopify Variant Id to SKU
Replaces sales order SKUs with variant Ids.
Save Order URI ID to Meta Var
Extracts URI from Shopify notes.
Calculate dispatch date using orderDate
Carrier map
SKU Lookup
Patchworks pulls fulfilled orders from Shopify and the dispatch is then sent to Virtualstock Supplier, with the associated tracking number.
We pull newly updated orders with a fulfilled
or partially-fulfilled
status and filters on source_name
= VS_Patchworks
for sales orders.
The operations count for this process flow is: 2 per fulfillment.
For reference, all shapes in this process flow are documented below. Do not change shape settings unless advised to do so in our installation guide.
Trigger
Connector
Filter
There should be no need to change any settings for this shape. For reference, required settings are:
Source instance
: N/A
Source endpoint
: N/A
Filters
: Set as: *.source_name
string
equals
VS_Patchworks
Keep matching
: ON
Flow control
There should be no need to change any settings for this shape. For reference, required settings are:
Source instance
: N/A
Source endpoint
: N/A
Batch level
: *
Batch size
: 1
Script
These settings should not be changed. For reference, required settings are:
Script
: Save Order URI ID to Meta Var
Version
: v5 (latest)
Flow control
There should be no need to change any settings for this shape. For reference, required settings are:
Source instance
: N/A
Source endpoint
: N/A
Batch level
: *.fulfillments
Batch size
: 1
De-dupe
There should be no need to change any settings for this shape. For reference, required settings are:
Source instance
: N/A
Source endpoint
: N/A
Entity
: Fulfillments
Behaviour
: Filter records
Data Pool
: FulfillmentOrder
Key field
: *.id
Behaviour
: JSON
Add to cache
These settings should not be changed. For reference, required settings are:
Cache
: (Flow run) FulfillmentOrder
Cache key
: FulfillmentOrder
Append
: OFF
Save all pages
: ON
Map
Connector
If instance credentials are provided as part of the blueprint installation, there should be no need to change any settings for this shape. For reference, the required settings are:
Source instance
: Virtualstock Supplier
Source endpoint
: POST Dispatch an order
Variables
: Set as OrderURI
/ [[meta.JLorderId]]
Load from cache
These settings should not be changed. For reference, required settings are:
Cache
: (Flow run) FulfillmentOrder
Cache key
: FulfillmentOrder
Fail on cache miss
: OFF
Load all pages
: ON
De-dupe
There should be no need to change any settings for this shape. For reference, required settings are:
Source instance
: N/A
Source endpoint
: N/A
Entity
: Fulfillments
Behaviour
: Track records
Data Pool
: FulfillmentOrder
Key field
: *.id
Behaviour
: JSON
Save Order URI ID to Meta Var
Extracts URI from Shopify notes.
Carrier map
SKU Lookup
The Shopify & Virtualstock Supplier blueprint includes everything you need to sync orders, fulfillments, and inventory between Virtualstock Supplier and Shopify. The high-level architecture is illustrated below:
Orders are pulled from Virtualstock Supplier and created in Shopify with a paid
and unfulfilled
status. When a fulfilment partner ships an order in Shopify, Patchworks pulls shipment information and sends this (together with a tracking number) to Virtualstock Supplier. Finally, inventory is synced from Shopify to Virtualstock Supplier.
Virtualstock & Shopify staging/sandbox credentials
Virtualstock Supplier credentials are provided by the associated Virtualstock merchant- e.g. John Lewis.
Virtualstock & Shopify live/production credentials
Virtualstock Supplier credentials are provided by the associated Virtualstock merchant- e.g. John Lewis.
List of all Shopify SKUs and corresponding Virtualstock Supplier part numbers
This will usually be in the form of a spreadsheet that's issued by the Virtualstock Supplier merchant. For example, John Lewis provide a spreadsheet named Smartsheet or JL SKUs. Note: for testing, you only require enough SKUs/part numbers to fulfill required tests.
List of Shopify carriers that will be used for Virtualstock Supplier orders
The Slug for these carriers is usually provided by the Virtualstock Supplier merchant (e.g. John Lewis).
Test scenarios
Some Virtualstock merchants mandate specific test scenarios - for example, John Lewis require three test orders to be processed before live/production credentials are released.
Confirmation of predefined values to be used for acknowledgement back to Virtualstock Supplier.
Supplier_delivery_date
. This is usually orderdate
plus 5-7 days
Fulfillment_route
. This is usually set to Direct to customer
.
In Patchworks, an operation is counted whenever a request is made to send or receive a payload to/from an endpoint. The operations count for installed process flows is shown below:
4 per order
Every 10 minutes
2 per fulfillment
Hourly
3 per sync
2 x daily
* You can change the frequency at which process flows run - please see our installation guide for details.
Please see our installation guide.
Please see our available process flows section.
Cancellations both from Virtualstock Supplier and From Shopify
Returns/Refunds
Product Creation
Lead Time updates to Virtualstock Supplier
Having installed the blueprint, edit this shape and define your preferred run schedule. Please see the for specific notes.
Generally, field mappings should not be changed. However please refer to the for any fields that are noted for special attention.
Source instance
: None
Source endpoint
: None
Generally, field mappings should not be changed. However please refer to the for any fields that are noted for special attention.
Source instance
: None
Source endpoint
: None
Takes Shopify's order created date and adds 5 days to calculate the supplier delivery date. If required, you can change the number of days used for this calculation - please see the for details.
Maps Shopify tracking companies to Virtualstock carriers (and vice versa). You need to update this table with your own values - please see the for details.
Maps Virtualstock Supplier part numbers to Shopify SKUs. You need to update this table with your own values - please see the for details.
Having installed the blueprint, edit this shape and define your preferred run schedule. Please see the for specific notes.
This shape includes parameters that you should review/update. Please see the for specific notes.
Source instance
: Shopify
Source endpoint
: GET Retrieve a list of orders
Parameters
: created_at_min
financial_status
status
fulfillment_status
updated_at_min
Generally, field mappings should not be changed. However please refer to the for any fields that are noted for special attention.
Source instance
: None
Source endpoint
: None
Maps Shopify tracking companies to Virtualstock carriers (and vice versa). You need to update this table with your own values - please see the for details.
Maps Virtualstock Supplier part numbers to Shopify SKUs. You need to update this table with your own values - please see the for details.
If you are a user with an administrator or manager role, you can update general details for any existing user accounts associated with your company profile.
Step 1 Access the user list for your company profile.
Step 2 Move down to the extra section - you'll see a [company] users tab showing all existing user accounts. At a glance you can see each user's name, email address and role - click the name of the user that you want to update:
Step 3 Update the general details section as required:
Step 4 Click the save button at the bottom of the page.
If you are a multi-company profile user with permission to manage another linked company, you can view and manage users associated with your own company profile.
Step 1 Log into the Patchworks dashboard using your own Patchworks credentials and ensure that you are switched into your own company profile.
Step 2 In the top, left-hand corner click the arrow associated with your company name - then select your profile:
Step 3 Move down to the extra section, where all users for your multi-company profile are displayed:
Step 4 From here you can select any user's name to access and manage their profile.
If you are a multi-company profile user with permission to manage another linked company, you can see who else in your team also manages that company.
Step 1 Log into the Patchworks dashboard using your own Patchworks credentials.
Step 2 Switch into the managed company that you want to review.
Step 3 Click the arrow associated with the company name and select the [company] profile option - for example:
Step 4 Move down to the extra section and select the team members with access tab:
Step 5 All team members are displayed and you can see which users have permission to manage the current company, and which do not:
For information about granting and revoking access to the current company please see our Granting & revoking permission for a team member to manage a company guide.
If you are a multi-company profile user with permission to manage another linked company (i.e. your own user account is associated with a manager or administrator role and you have been granted permission to manage the company in question), you can grant and revoke permission for other team members to manage the same company.
Step 1 Log into the Patchworks dashboard using your own Patchworks credentials and ensure that you are switched into your own company profile.
Step 2 Access the list of team members for your company.
Step 3 Click the name of the user that you want to update:
Step 4 Move down to the extra panel and click the managed companies tab:
All companies that are linked to yours for management are listed:
Step 5 The next step depends on the action that you wish to take:
Step 6 Save the company profile.
If you are a multi-company profile user with permission to manage another linked company, you can view and manage user accounts that are directly associated with a company that you manage. These are sometimes referred to as 'native' company users. You can:
For more information about 'native' company users and agency/partner team members please see our managed company users introduction.
If you are a multi-company profile user with permission to manage another linked company, you can add new team members to your own company profile. Once a user is added you can (if required) go on to grant them permission to manage other companies.
For a new user to manage linked companies, they must be assigned the manager
role. To set this role, your own user account must be associated with the administrator role.
Step 1 Access team members for your own company profile.
You must be logged in with an administrator account to complete these steps.
Step 2 Click the create user button:
Step 3 Enter the person's name and email address:
The email address provided here is used to log into the Patchworks dashboard.
Step 4 Click the save button. The user account is saved and an email is sent to the given address, with a link for the user to set their password.
A password must be used with the user's email address in order to log into the Patchworks dashboard.
Step 5 The user roles tab is displayed and you'll see that the new account is created - by default, new accounts are created with a user role:
Permission to manage other companies can only be granted for team members with a manager role, so you need to assign this role now.
Step 6 Click the assign role button against the manager role:
If your user account isn't associated with an administrator role, you won't be able to make this change.
Step 7 Click the remove role button for the user role:
Step 8 When prompted, confirm this change.
Step 9 Save changes.
Step 10 If required, you can now go on to grant this user access to manage any companies that you currently manage.
If you are a multi-company profile user with permission to manage another linked company, you can trigger a password reset email for users associated with a company that you manage.
When this is done, a reset email is sent to the email address for the user, containing a reset link. Password reset links are valid for 24 hours. After this, another password reset must be triggered so a new link is emailed.
Step 1 Access company users for the required linked company.
Step 2 Move down to the extra section and select the [company] users tab - here you will find all 'native' user accounts associated with this company - i.e. users who are directly associated with this company profile and can log into the Patchworks dashboard with their own credentials:
Step 3 Click the name of the user that requires a password reset:
Step 4 Move down to the extra section and select the [company] users tab - here you will find all users who are directly associated with this company profile (and can log into the Patchworks dashboard with their own credentials):
Step 5 Click the name of the user account that you want to access:
Step 6 Click the reset password button at the top of the page:
Step 7 The user will receive an email from Patchworks which includes a link to change their password.
When a , assigning them a role is part of the initial account creation process. Steps detailed on this page can be followed if you need change the role(s) for an existing team member.
If you are a multi-company profile user with an administrator
or manager
role, you can change the role associated with other lesser-role team members. The following rules apply:
For more information please see our page.
Step 1 .
Step 2 Click the name of the user account that you want to update:
Step 3 The user roles tab is displayed and you'll see which roles are currently assigned for this account:
Step 4 Assign (and/or remove) roles as needed by clicking the appropriate assign role / remove role button.
Step 5 Save changes.
The connectors page allows you to browse, and all prebuilt connectors - these are 'standard' connectors that Patchworks builds and maintains.
When you install a connector, it is added to - from here you can (authenticated with your credentials for that system) and then start working with these as .
If you need to connect a system which does not exist in the marketplace and you have an understanding of APIs and data structures, you can build your own connector with our (perhaps starting from a if a Postman collection is available).
Having selected the connectors option from the marketplace, you can browse and prebuilt connectors:
Connectors are displayed as tiles over a series of pages, which you can step through using page numbers at the bottom of the marketplace. Each connector includes general details and an option:
For all information about working with connectors and instances, please see our section.
Administrator
Can promote accounts to roles up to and including manager
level (e.g. change a user
account to a manager
account).
Can reduce other non-administrator accounts to a lesser role (e.g. change a manager
account to a user
account).
Manager
Can promote accounts to roles up to and including user
level (e.g. change a read-only
account to a user
account).
Can reduce other non-manager accounts to a lesser role (e.g. change a user
account to a read-only
account).
The cross-reference lookups page includes a range of prebuilt cross-reference lookup tables. These perform a range of conversions which you can apply via a map field transformation.
Having selected the cross-reference lookups option from the marketplace, you can browse and install cross-reference lookup tables:
Tables are displayed over a series of pages, which you can step through using page numbers at the bottom of the marketplace. Each item is displayed with a name, description and an install option.
For all information about working with cross-reference lookups, please see our Cross-reference lookups section.
The scripts page includes a range of prebuilt custom scripts. These scripts perform a range of functions that you may find useful when building process flows.
Having it can be used in your process flows immediately, via the .
Having selected the scripts option from the marketplace, you can browse and prebuilt scripts:
Having created and saved a cross-reference lookup, you can upload it to the cross-reference lookups section of your private marketplace. This guide walks through the steps needed to achieve this.
You only need to upload a cross-reference lookup to your private marketplace if you want to make it available for your users (and your linked company users) to download as a standalone resource.
If you just want to include the cross-reference lookup in a process flow or an app, you don't need to upload it separately - please see or .
Step 1 Login to the Patchworks dashboard and ensure you're switched to the correct company profile.
Any resources you upload to the private marketplace for your own 'parent' company will be available to your 'child' companies (via their private marketplaces). Similarly, any resources uploaded to the private marketplace for a 'child' company will be available to the 'parent' company AND all child-sibling companies. For more information please see .
Step 2 From the left-hand navigation menu, select the cross-reference lookups option - all of your cross-reference lookups are listed.
Step 3 Click the name of the lookup that you want to upload, to access details, then click the upload button:
Step 4 The upload is queued for processing and will be completed as soon as possible.
Scripts are displayed over a series of pages, which you can step through using page numbers at the bottom of the marketplace. Each item is displayed with a name, description and an option.
For all information about working with custom scripts, please see our section.
If you don't see an upload option, it's likely that your user account does not have the required permissions. Please if this is the case.
Check your for confirmation if you miss the popup message when this is done.
A blueprint can include any number and combination of the following components:
A blueprint will always include at least one process flow.
Each blueprint in your marketplace is displayed with a visual summary of what's included - for example:
For more information about this summary please see The Patchworks marketplace.
If you click on a blueprint tile, you can see a detailed breakdown of what's included:
From here you can:
Any connectors included with the blueprint are installed as part of the install process. To use these connectors in process flows, you must add an instance of each - this is where you provide your authentication credentials for the associated third-party system.
If you have your credentials to hand, add them now using the add instances options provided - for example:
You are prompted to choose an authentication method and then enter your credentials - for example:
When you save instance details and then install the blueprint, these instances are created as part of the installation. As a result, all connector shapes in process flows will be configured with these instances automatically.
It's not mandatory to add your instances as part of the blueprint installation. You can install the blueprint and add instances afterwards via your manage connectors page. If you do this, you must apply these instances to process flow connector shapes manually.
You cannot add instances that require OAuth 2 (Client Credentials) authentication, via the blueprint install process. If a blueprint includes connectors that require OAuth 2 (Client Credentials) authentication then you should install the blueprint and add instances afterwards via your manage connectors page. If you do this, you must apply these instances to process flow connector shapes manually.
If a blueprint includes a process flow that you're sure you don't need, you can prevent it from being installed here - clicking the install button toggles to don't install:
Typically, process flows are key to the successful implementation of blueprints. We recommend installing all included process flows unless you have a specific reason not to do so.
All connectors used in process flows are installed. Prior to installation, you can choose to - or you can just install the connectors and add instances later. If the blueprint includes a connector that you have already installed from the , a fresh copy of that connector is added alongside the existing one. You can then decide which one to use.
All scripts defined in process flow and/or are installed and deployed, ready for use.
All cross-reference lookups defined as process flow are installed and ready for use.
Any data pools defined in process flow are added. These are 'clean' data pools (i.e. with no associated data), ready for use.
Any caches and cache keys defined in process flow are added. These are 'clean' caches (i.e. with no associated data), ready for use.
Microservices are used to build the Patchworks platform - small, independent services that communicate with each other, allowing for flexibility, scalability, and easier maintenance.
API first is key for powerful integrations. Our next-generation dashboard is driven by powerful APIs which means we can integrate with any other API simply and seamlessly.
Cloud-native development facilitates our microservice architecture, Kubernetes deployments, DevOps infrastructure as code, and much more!
Headless is exactly what you'd expect for an API-first platform. The Patchworks backend is built with our own API, which is then consumed by the dashboard for general use.
Real-time logs (via web sockets) can be viewed while a process flow runs, with visibility of request, response and payload information at every step.
Logs are retained for one month for retrospective problem-solving.
Webhooks, events, and inbound API requests can all be tracked through the Patchworks Dashboard - you don’t need to be an engineer to figure out when/where execution errors occur.
We manage all API updates for our library of prebuilt connectors.
We take care of all supported authentication mechanisms (OAuth, token, API key, etc.).
We've removed all the complexity when it comes to building and maintaining new integrations.
Our multi-tenant architecture means that customers have the benefits of shared software and infrastructure, secure in the knowledge that each customer's data is isolated and invisible to other tenants.
Multi-tenancy provides a much faster solution, since we only search one set of data rather than everything - all database operations and secret storage is per-tenant.
Multi-tenancy allows flexibility for change - if necessary we can 'lift and shift' a tenant to a new database, or to a faster region, or even to a completely different cloud provider in a different continent!
Infrastructure updates are made via IaC (Infrastructure as Code).
Infrastructure updates are peer-reviewed and authorised before being merged.
All production code flows through development and staging review cycles before release to production.
Every release must pass both automated and hands-on testing by our QA team.
Product penetration testing is performed annually by an external, CREST-accredited organisation.
Our Kubernetes nodes live in private subnets.
All key ingresses are IP whitelisted.
We adopt a 'least privilege' model for our development team, and also for users of our AWS and Kubernetes infrastructure.
All key business systems must be accessed via a VPN
All staff use LastPass to generate and store strong passwords - 2FA access to LastPass is mandated.
Access is managed via role-based permissions, so only authorised users can access integrations and data for their company profile(s).
Audit logs provide a complete history of all user account activity, including Patchworks users.
Users always control their own passwords - password resets are never performed on behalf of other users.
Single sign-on via Google is supported.
(1) Identify interactions Every time a shape in your process flow performs a manipulation, moves data or sends/receives data between systems, an interaction occurs. This could be an API call, a file upload, or any other data transfer/manipulation.
(2) Measure payload sizes For each interaction, the size of the payload out is measured in megabytes.
Only the actual payload is considered - metadata, headers, and other non-payload data are NOT considered when calculating the payload out size.
(3) Aggregate payload sizes All payload sizes are aggregated to calculate the total data usage.
Bob is assigned the manager
role
By default, the manager
role has required permissions to create and update custom scripts
Bob's company is associated with a standard
subscription tier, which permits read-only access to existing custom scripts and other advanced features
Bob can view any existing custom scripts (for example, that have been installed via blueprints), but he cannot make any changes and he cannot create his own scripts
Jack is assigned the manager
role
By default, the manager
role has required permissions to create and update custom scripts
Jack's company is associated with a professional
subscription tier, which permits full access to custom scripts and other advanced features
Jack can view, create and update custom scripts as needed
The system continuously monitors traffic and resource usage (CPU, memory).
When usage exceeds predefined thresholds, the auto-scaler triggers.
Additional resources/pods are deployed to handle the increased load
When demand drops, resources are reduced to optimise costs.
We use AWS RDS for all critical databases. Our databases have full redundancy with one ‘read’ and one ‘write’ copy of each.
Each database copy is hosted in a separate availability zone so, in the unlikely event of a failure in one zone, we can fall back to the other.
In the simplest of flows, a connector shape receives a 1MB payload, so the first payload out is 1MB.
The map shape receives this as its incoming payload. There are no field transformations so the data doesn't change - the second payload out is 1MB.
The final connector shape receives this as its incoming payload to be sent into the associated system. We have NOT set the save response as payload option to on
, so the payload out is 1MB.
The aggregate total for the payload out size for all three shapes is 3MB.
Here, a connector shape receives a 1MB payload, so the first payload out is 1MB.
The de-dupe shape receives this as its incoming payload and filters out all duplicate records, reducing the payload size. The next payload out is 0.75MB.
The map shape receives this as its incoming payload. There are no field transformations so the data doesn't change - the next payload out is 0.75MB. The flow control shape receives this as its incoming payload and batches it into 10 payloads for onward processing. The next payload out is 10 x 75K.
The second connector receives all 10 payloads to be sent into the associated system. We have NOT set the save response as payload option to on
, so the payload out is 10 x 75K. Finally, all 10 payloads pass through the de-dupe shape for tracking only. The payload out is 10 x 75K.
The aggregate total for the payload out size for all shapes is 4.75MB.
Here, a connector shape receives a 1MB payload, so the first payload out is 1MB.
This payload is added to a cache, and the next payload out is 1MB. This payload is passed to a route shape with conditions that send half the payload down one route and half down the other - resulting in 2 x 0.5MB payloads out.
For route 1, the first 0.5MB payload passes through a track data shape and the payload out is 0.5MB. The map shape receives this as its incoming payload and there are no field transformations so the data doesn't change - the payload out is 0.5MB. The final connector receives this as its incoming payload to be sent into the associated system. We have NOT set the save response as payload option to on
, so the payload out is 0.5MB.
For route 2, the first 0.5MB payload is received by the map shape - there are no field transformations so the data doesn't change - the payload out is 0.5MB. The final connector receives this as its incoming payload to be sent into the associated system. We have NOT set the save response as payload option to on
, so the payload out is 0.5MB.
The aggregate total for the payload out size for all shapes is 5.5MB.
Here, a connector shape receives a 1MB payload, so the first payload out is 1MB.
This payload is added to a cache, and the next payload out is 1MB. Then we load cache data from an existing company cache which is 50MB, so the next payload out is 50MB.
The script shape receives this as its incoming payload and runs - it doesn't do anything that affects the payload size so the next payload out is 50MB.
The map shape receives this as its incoming payload. There are no field transformations so the data doesn't change - the next payload out is 50MB.
The final connector receives this as its incoming payload to be sent into the associated system. We have NOT set the save response as payload option to on
, so the payload out is 50MB.
The aggregate total for the payload out size for all shapes is 202MB.
In the simplest of flows you might receive 1 payload from a source endpoint which contains 350 records in a single, unpaginated payload. The flow goes on to send that payload to a destination endpoint.
This results in 2 operations - 1 for the receive operation and 1 for the send operation.
In a slightly more complex flow you might receive 1 payload from a source endpoint which contains 350 records in a single, unpaginated payload.
This results in 6 operations - one for the receive operation and 5 for the send operations.
In this example our incoming data is paginated as 50 records per page, so we receive 350 records as 7 payloads (50 records in each).
The flow goes on to send all of these payloads to a destination endpoint.
This results 14 operations - 7 for receive operations and 7 for send operations.
In this example our incoming data is paginated as 50 records per page, so we receive 350 records as 7 payloads (50 records in each).
This results 357 operations - 7 for receive operations and 350 for send operations.
Sync sales orders, fulfillments, and inventory between Shopify and Virtualstock Supplier.
Kubernetes pod and node auto-scaling Ensure that integrations run consistently, even in the busiest times. See our page for more information.
The flow continues with a shape which batches this data into smaller chunks, resulting in 5 payloads, each containing 70 records. The flow goes on to send all of these payloads to a destination endpoint.
The flow continues with a shape which batches this data into single-item payloads. The flow goes on to send all of these payloads to a destination endpoint.
is the Warehouse Management System for eCommerce businesses, online retailers and direct to consumer brands.
is a cloud-based, fully hosted commerce platform which can be used to create and manage online stores.
(formerly Vend) is a retail POS, inventory management, and eCommerce solution.
is a cloud-based, fully hosted commerce platform which can be used to create and manage online stores.
is a cloud-based solution that helps businesses manage all aspects of their operations.
is a cloud-based, fully hosted commerce platform which can be used to create and manage online stores.
is a cloud-based, fully hosted commerce platform which can be used to create and manage online stores.
provides complete supply chain solutions, specialising in transportation, logistics, forwarding and warehousing.