Description

Aero Commerce is a performance-based platform that's extendable and scalable, providing bespoke, personalised eCommerce stores for retailers.

Authentication

When adding connector instances for Aero Commerce, the following authentication methods are supported:

• Token authentication

Token authentication

When a user chooses to add a connector instance using token authentication, the credentials below are prompted:

Description

Akeneo is a product information management and product data intelligence solution.

API documentation

API documentation for Akeneo (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Akeneo, the following authentication methods are supported:

Akeneo Auth

Description

Adobe Commerce (formerly Magento) is a flexible, scalable commerce platform that lets you create uniquely personalised B2B and B2C experiences.

API documentation

API documentation for Adobe Commerce (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Adobe Commerce, the following authentication methods are supported:

Token authentication

Description

Bleckmann provides a seamless logistics process, from warehousing and inventory management to order fulfilment.

API documentation

API documentation for Bleckmann (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Bleckmann, the following authentication methods are supported:

Token authentication

Description

Bloomreach Engagement is an eCommerce platform specialising in marketing automation, product discovery, and content management systems.

API documentation

API documentation for Bloomreach (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Bloomreach, the following authentication methods are supported:

Basic authentication

Description

Algolia is a search-as-a-service API that focuses on providing the best experience for end users.

Authentication

When adding connector instances for Algolia, the following authentication methods are supported:

• API key

API key authentication

When a user chooses to add a connector instance using API key authentication, the credentials below are prompted:

SecretDescription

Brightpearl is a Retail Operating System (ROS) for retailers and wholesalers.

API documentation

API documentation for Brightpearl (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Brightpearl, the following authentication methods are supported:

• OAuth 2 (authorisation code)

OAuth 2 (authorisation code)

When a user chooses to add a connector instance using OAuth 2 (authorisation code) authentication, the credentials below are prompted:

Description

Avasam is a dropshipping platform for retailers and sellers in the UK.

API documentation

API documentation for Avasam (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Avasam, the following authentication methods are supported:

• OAuth 2 (client credentials)

OAuth 2 (client credentials)

When a user chooses to add a connector instance using OAuth 2 (client credentials) authentication, the credentials below are prompted:

Description

ChannelEngine ensures product info and stock levels are synchronised across marketplaces - syncing product information, product data and stock information across channels.

API documentation

API documentation for ChannelEngine (used to build this connector) can be found via the link below:

Swagger documentation is available by composing your own company-specific link (using your ChannelEngine tenant subdomain) as below:

https://<tenant subdomain>.channelengine.net/api/swagger/index.html

For example:

https://patchworks-dev.channelengine.net/api/swagger/index.html

Authentication

When adding connector instances for ChannelEngine, the following authentication methods are supported:

• Token authentication

Token authentication

Description

Airtable is a single platform which empowers teams to build custom apps on top of shared data.

API documentation

Airtable's API documentation (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Airtable, the following authentication methods are supported:

• Token authentication

Token authentication

When a user chooses to add a connector instance using token authentication, the credentials below are prompted:

Description

Cin7 is a fully integrated, cloud-based inventory management solution that streamlines stock management across multiple channels.

API documentation

API documentation for Cin7 (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Cin7, the following authentication methods are supported:

• Login & password

Login & password authentication

When a user chooses to add a connector instance using Login & password authentication, the credentials below are prompted:

Description

Centra is a commerce platform for fashion & lifestyle brands.

API documentation

API documentation for Centra (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Centra, the following authentication methods are supported:

• API key

API key authentication

When a user chooses to add a connector instance using API key authentication, the credentials below are prompted:

Description

Clarus WMS is a leading provider of warehouse management systems for businesses.

API documentation

API documentation for Clarus WMS (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Clarus WMS, the following authentication methods are supported:

• Basic authentication

Basic authentication

When a user chooses to add a connector instance using basic authentication, the credentials below are prompted:

Description

is a (SaaS) platform that helps retailers improve in-store shopping experiences by combining digital assets with physical stores.

API documentation

API documentation for Cloudshelf (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Cloudshelf, the following authentication methods are supported:

Token authentication

Description

Commerce Layer is an API-first commerce engine that makes it easy to incorporate full eCommerce functionality into your existing tech stack.

API documentation

API documentation for Commerce Layer (used to build this connector) can be found via the links below:

Authentication

When adding connector instances for Commerce Layer, the following authentication methods are supported:

OAuth 2 (client credentials)

Description

BigCommerce is a cloud-based eCommerce platform, providing software as a service services to retailers.

API documentation

API documentation for BigCommerce (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for BigCommerce, the following authentication methods are supported:

Token authentication

Description

Deposco is an inventory management system for retail, eCommerce, DTC & 3PL users.

API documentation

API documentation for Deposco (used to build this connector) can be found via the link below:

You must be logged in to access this API documentation.

Authentication

When adding connector instances for Deposco, the following authentication methods are supported:

• Basic authentication

Basic authentication

When a user chooses to add a connector instance using basic authentication, the credentials below are prompted:

Description

Microsoft Dynamics 365 Business Central is a cloud-based ERP solution.

API documentation

API documentation for Business Central (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Business Central, the following authentication methods are supported:

• OAuth 2 (client credentials)

OAuth 2 (client credentials)

When a user chooses to add a connector instance using OAuth 2 (client credentials) authentication, the credentials below are prompted:

Introduction

Having installed the Cybertill connector, some setup is required before it can be used. You must:

• Stage 1: Create a post-request script

• Stage 2: Apply the post-request script to your Cybertill connector

Once this setup is complete, you can add instances for use in process flows.

Stage 1: Creating a post-request script

A post-request script is required to generate an authentication token from the given instance credentials. Follow the steps below to create this script.

Step 1 From the Patchworks dashboard, select scripts from the left-hand navigation menu.

Step 2 Click the create script button:

Step 3 In the name field, type the following:

Cybertill Post-Request Script

Step 4 In the description field, type the following:

Cybertill Auth Token Generator - Post Script

Step 5 Click in the language field and select PHP 8.1:

Step 6 Click the create button.

Step 7 The script is created and opened in edit mode - select and remove any placeholder code:

Step 8 Paste in the code below.

Step 9 Click the save and deploy button:

Step 10 Click the scripts element of the breadcrumb trail to exit back to your list of scripts and go to the next stage:

Stage 2: Applying the post-request script

Step 1 From the Patchworks dashboard, select connectors and instances from the left-hand navigation menu to access your installed connectors.

Step 2 Find your Cybertill connector and click the settings icon.

Step 3 Click the authentication option:

Step 4 Select the SOAP authentication method:

Step 5 In the lower panel, select the post-request script tab:

Step 6 Click in the select script field and select your Cybertill Post-Request Script:

Step 7 Select the latest version:

Step 8 Save changes:

Step 9 You can now add instances of this connector for use in process flows.

Description

Cybertill is a cloud-based retail software provider which incorporates eCommerce, stock control, CRM, merchandising and warehousing modules.

API documentation

API documentation for Cybertill (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Cybertill, the following authentication methods are supported:

• SOAP request authentication

SOAP request authentication

When a user chooses to add a connector instance using SOAP request authentication, the credentials below are prompted:

Required Additional setup

Having installed the Cybertill connector, some additional setup is required before it can be used. You need to create a post-request script and apply this to the connector.

Having completed this setup, the Cybertill connector is ready to use.

Introduction

When you install the Peoplevox connector from the Patchworks marketplace, pre and post authentication scripts are included.

Typically, you don't need to do anything with these scripts - they do what they need to do 'out of the box'. However, if you are connecting to a US region, you might need to update the pre-auth script.

What needs to be changed?

The pre-authentication script encodes passwords as Base64, which is required by most PVX regions. However, the US region requires this in plain text.

If you experience issues with authentication - usually a message like 'System : Security - Invalid Session', then you should update the pre-authentication script to remove Base64 encoding. This is a simple change, summarised below.

The Steps

Required steps are detailed in the following sections:

• Stage 1: Update the Peoplevox pre-auth script

• Stage 2: Apply the Peoplevox pre-auth script to your connector

Stage 1: Update the Peoplevox pre-auth script

Step 1 From the Patchworks dashboard, select process flows | scripts from the left-hand navigation menu.

Step 2 From the installed section, click the pre-auth Base64 encode script name:

Step 3 Once the script is open in edit mode, move down to the code editor and change:

base64_encode($matches[1]) 

to:

$matches[1] 

Step 4 Save and deploy the script:

Stage 2: Apply the Peoplevox pre-auth script to your connector

Step 1 From the Patchworks dashboard, select process flows | connectors & instances from the left-hand navigation menu.

Step 2 Click the settings icon associated with the Descartes Peoplevox connector:

Step 3 Select the authentication option:

Step 4 Click the SOAP Authentication method:

Step 5 Select the pre-request script tab:

Step 6 Select the latest version of the script:

Step 7 Save changes.

Description

Commercetools provides all composable components needed to build and run shopping experiences.

API documentation

API documentation for Commercetools (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Commercetools, the following authentication methods are supported:

• OAuth 2 (client credentials)

OAuth 2 (client credentials)

Description

Clerk.io is an e-commerce personalisation platform that helps e-commerce businesses analyse customer behaviours.

API documentation

API documentation for Clerk (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Clerk.io, the following authentication methods are supported:

• Key

Key authentication

When a user chooses to add a connector instance using key authentication, the credentials below are prompted:

Description

Descartes Peoplevox is the Warehouse Management System for eCommerce businesses, online retailers and direct to consumer brands.

API documentation

API documentation for Peoplevox (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Peoplevox, the following authentication methods are supported:

• SOAP request authentication method

SOAP request authentication

Required Additional setup

SetData script

Before this connector can be used as a target connection in process flows, you must create a setData script.

Having completed this setup, the Peoplevox connector is ready to use.

Pre-authentication script

If you are connecting to a US region, you might need to update the default pre-authentication script for the installed connector. For information, please see Peoplevox pre & post authentication scripts page.

Using the Peoplevox connector in process flows

The Peoplevox connector is like any other Patchworks connector - it gets added to process flows via a connection shape.

However, if you build a process flow with Peoplevox as a target connection, you must add a custom script shape and apply the setData script immediately before the target connection shape. For more information please see: Using the Peoplevox setData script in process flows.

Introduction

Having installed the Peoplevox connector and applied pre and post request scripts, you're ready start using the connector in process flows.

If you build a process flow with Peoplevox defined as a target connection shape, you must always include a script shape immediately before the connection shape, and associate this with the setData custom script. This script takes care of data conversions that are required before sending data into Peoplevox.

The steps

Step 1 Build your process flow in the usual way, including a connection shape configured for Peoplevox as a target.

Step 2 Immediately before the Peoplevox connection, add a script shape - for example:

Step 3 In custom script settings, select the PVX setData script:

Step 4 Save the shape - the script is added to you flow:

Introduction

If you are pulling data from Peoplevox (i.e. your process flow includes a connection shape configured with a Peoplevox GET endpoint), a search option is available. For example:

Using the search field

You can use this field to filter data via the API, using syntax detailed in the Peoplevox API documentation.

Introduction

If you're building a process flow with Peoplevox as a target connection, you must create a setData script and then - in your process flow - apply this script immediately before the target connection.

Creating a setData script

Step 1 From the Patchworks dashboard, select scripts from the left-hand navigation menu.

Step 2 Click the create script button:

Step 3 In the name field, type the following:

PVX SetData

Step 4 In the description field, type the following:

Convert flat Json payload to csv SetData format

Step 5 Click in the language field and select PHP 8.1:

Step 6 Click the create button:

Step 7 The script is created and opened in edit mode - select and remove the placeholder code:

Step 8 Paste in the code below.

Step 9 Click the save and deploy button:

Introduction

If you are pulling data from Peoplevox (i.e. your includes a configured with a Peoplevox GET endpoint), the payload is generated as XML data.

If required, you can convert the XML payload to JSON by adding the script to a immediately after the Peoplevox . For example:

Custom script - XML to JSON

The script below will convert any Peoplevox XML payload, irrespective of the entity type being pulled.

Description

EKM Insight is a leading managed print service (MPS) software supplier, helping customers optimise print and imaging operations.

API documentation

API documentation for EKM Insight requires EKM Insight login credentials.

Authentication

When adding connector instances for EKM Insight, the following authentication methods are supported:

API key & bearer authentication

When a user chooses to using API key & bearer authentication, the credentials below are prompted:

Description

Dotdigital is a Software-as-a-Service (SaaS) marketing platform that integrates with key business systems (including eCommerce platforms and CRMs) to enable data-driven, automated campaigns and rich, real-time insights.

API documentation

API documentation for Dotdigital (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Dotdigital, the following authentication methods are supported:

Basic authentication

Description

EdiFabric is a developer SDK and API used to parse, generate, validate, split, acknowledge, represent, view, and document EDI files.

API documentation

API documentation for EdiFabric (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for EdiFabric, the following authentication methods are supported:

Subscription key authentication

Description

Emarsys is a customer engagement platform that helps marketers in a range of industries deliver personalised experiences.

API documentation

API documentation for Emarsys (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Emarsys, the following authentication methods are supported:

Token authentication

Required Additional setup

Having completed this setup, the Emarsys connector is ready to use.

Introduction

Having , some setup is required before it can be used. You must:

Once this setup is complete, you can for use in .

Stage 1: Creating a pre-request script

A pre-request script is required to generate an authentication token from username and password credentials. Follow the steps below to create this script.

Step 1 From the Patchworks dashboard, select scripts from the left-hand navigation menu.

Step 2 Click the create script button:

Step 3 In the name field, type the following:

Step 4 In the description field, type the following:

Step 5 Click in the language field and select PHP 8.1:

Step 6 Click the create button:

Step 7 The script is created and opened in edit mode - select and remove any placeholder code:

Step 8 Paste in the code below.

Step 9 Click the save and deploy button:

Step 10 Click the scripts element of the breadcrumb trail to exit back to your list of scripts and go to the next stage:

Stage 2: Applying the pre-request script

Step 1 From the Patchworks dashboard, select connectors and instances from the left-hand navigation menu to access your installed connectors.

Step 2 Find your Emarsys connector and click the settings icon:

Step 3 Click the authentication option:

Step 4 Select the token authentication method.

Step 5 Select the pre-request script tab:

Step 6 Click in the select script field and select your Emarsys Pre-Request Script:

Step 7 Select the latest version:

Step 8 Save changes:

Description

Fluent Commerce is a leading order management system which optimises fulfillment and solves inventory visibility issues.

API documentation

API documentation for Fluent Commerce (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Fluent Commerce, the following authentication methods are supported:

OAuth 2 (client credentials)

Description

Flexport focuses on supply chain management and logistics, including order management, delivery, trade financing, insurance, freight forwarding and customs brokerage.

API documentation

API documentation for Flexport (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Flexport, the following authentication methods are supported:

OAuth 2 (client credentials)

Description

Freshdesk is a cloud-based customer engagement solution for streamlining customer support.

API documentation

API documentation for Freshdesk (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Freshdesk, the following authentication methods are supported:

API key authentication

Description

EVA's cloud-based solution combines (m)POS, e-commerce, clienteling, order management, and inventory & fulfillment.

Authentication

When adding connector instances for EVA, the following authentication methods are supported:

Token authentication

When a user chooses to using token authentication, the credentials below are prompted:

Introduction

Having installed the Google Sheets connector and added required instances (using credentials obtained via the Google Sheets APIs and Services portal), you can add this connector to process flows, syncing data to/from your spreadsheets.

This page provides guidance and techniques for using the Google Sheets connector in process flows.

Connector settings

Having added a connector shape to your process flow and selected a Google Sheets source instance and endpoint, you'll see that variables are available - for example:

Specific variables will vary according to which source endpoint is selected but essentially, this is where you define which spreadsheet to access and then additional details (for example, target cell range).

Finding your spreadsheet id

Whichever endpoint you select, you'll always need to enter a value for a spreadsheet id variable. Every Google Sheets spreadsheet has a unique id, which you can find by opening the spreadsheet and checking the URL. Here you'll find a long string of characters after base URL - for example:

This string of characters (everything between the two / characters) is your spreadsheet id.

Example: Retrieving data

For this example, we have a simple product list in a spreadsheet:

In the steps below we'll walk through the process of sending data from columns E, F, G, H, and I into a destination database.

Prerequisites

• Ensure you've completed the required setup in your Google Workspace to obtain OAuth 2.0 credentials.

• Ensure that the Google Sheets connector is installed from the Patchworks marketplace.

• Ensure that at least one instance has been created for this connector, using your OAuth 2.0 credentials for authentication.

The steps

Step 1 Create a new process flow and add a connector shape. Configure the

For example:

Step 2 If we run the flow now and check payload information for the connector step, we can see data from the spreadsheet:

The first thing to note is that the majorDimension is set to ROWS:

majorDimension is a Google Sheets API parameter that determines how values are structured - it might be set to ROWS or COLUMNS (ROWS is the default if nothing is defined). In Patchworks, this value is set in the schema for each Google Sheets endpoint.

Taking our example, we can see that each row in our sheet is output as an array containing items for each column. Let's look at this structure in a bit more detail.

In our spreadsheet, columns are organised from A to I:

But in our payloads, these column labels aren't shown:

To target columns or rows, we use numbers. For rows this is straightforward - by default, every row in a sheet has a unique number. But for columns we must translate existing alpha labels to numbers, starting at 0. So our columns A to I can be referenced as 0 to 8:

You'll see how this works in subsequent steps.

Step 3 Now we've connected to our Google Sheet and pulled a single payload that contains all rows. To send this data to our destination system, we need to break that payload into smaller batches, with one record (i.e. row) per payload. To achieve this, we add and configure a flow control shape:

Here, we're saying that we want to target records within the values array and create batches of 1 - i.e. create one payload for every row. We also toggle the Do not wrap single items in an array option ON, because our destination system requires this.

Now if we run the flow and check the output, we have multiple payloads:

...each containing data for a single row:

Step 4 Next, we add a connector for our destination system:

Step 5 Finally, we add a map shape and define field mappings to determine where our column values are placed in the destination system - this is where our numbering system for column labels is needed:

Step 6 At the end of the mappings page, we toggle the wrap input payload option to ON, so our data is in the required format for our destination system.

Step 7 Having saved field mappings we can run the flow and check resulting payloads for the map step - here we see that our spreadsheet columns are successfully mapped to destination fields.

Step 8 If we check our destination database, all spreadsheet rows have been added:

Useful information

• Google Sheets API overview

Description

Gorgias is a customer support platform built for eCommerce companies.

API documentation

API documentation for Gorgias (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Gorgias, the following authentication methods are supported:

• Basic authentication

Basic authentication

When a user chooses to add a connector instance using basic authentication, the credentials below are prompted:

Description

GXO Logistics is a leader in cutting-edge warehousing and distribution - designing, managing, and optimising supply chains and delivering customised, tech-enabled solutions.

Authentication

When adding connector instances for GXO Logistics, the following authentication methods are supported:

• Basic authentication

Basic authentication

When a user chooses to add a connector instance using basic authentication, the credentials below are prompted:

Description

Google BigQuery is a fully managed enterprise data warehouse that helps you manage and analyze your data.

API documentation

API documentation for Google BigQuery (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Google BigQuery, the following authentication methods are supported:

• OAuth 2 (authorisation code)

OAuth 2 (authorisation code)

When a user chooses to add a connector instance using OAuth 2 (authorisation code) authentication, the credentials below are prompted:

Description

Fulfillmenttools is a SaaS solution, which handles all key fulfillment processes – from the management of incoming online orders and their distribution, to the picking of orders in-store and shipping or handover to the customer.

API documentation

API documentation for Fulfillmenttools (used to build this connector) can be found via the links below:

Authentication

When adding connector instances for Fulfillmenttools, the following authentication methods are supported:

• OAuth 2 (Google)

OAuth 2 (Google)

When a user chooses to add a connector instance using OAuth 2 (Google) authentication, the credentials below are prompted:

Description

Happy Returns (by PayPal) is a software and reverse logistics company that works with online merchants to handle product returns.

API documentation

API documentation for Happy Returns (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Happy Returns, the following authentication methods are supported:

• Token authentication

Token authentication

When a user chooses to add a connector instance using token authentication, the credentials below are prompted:

Description

Google Sheets is whatever you want it to be! Retrieve and update data from your sheets as needed.

API documentation

API documentation for Google Sheets (used to build this connector) can be found via the link below:

Authentication

When adding connector instances for Google Sheets, the following authentication methods are supported:

• OAuth 2 (client credentials)

OAuth 2 (client credentials)

When a user chooses to add a connector instance using OAuth 2 (client credentials) authentication, the credentials below are required:

Prerequisites

• You must have a Google Workspace account that's part of an organisation.

The steps

• Stage 1: Create a Google APIs and services project

• Stage 2: Configure a consent screen

• Stage 3: Create OAuth 2.0 credentials

• Stage 4: Apply OAuth 2.0 credentials to your OAuth playground

• Stage 5: Obtain a refresh token

Stage 1: Create a Google APIs and services project

Step 1 Access the Google APIs console - APIs and Services.

Step 2 If you haven't got an account already, go ahead and create one (use the Google account associated with the sheets you want to access).

Step 3 Click the create project button.

Step 4 Enter an appropriate name for this project (leave other settings as they default) and click the create button:

Stage 2: Configure consent screen

Step 1 Select OAuth consent screen from the left-hand navigation menu:

Step 2 Select the internal radio button and then click the create button:

Step 3 Complete app information:

The only mandatory fields are:

Step 4 Click save and continue.

Step 5 Click the add or remove scopes button:

Step 6 Add the following in the manually add scopes section:

https://www.googleapis.com/auth/spreadsheets

...then select add to table:

Step 7 Click the update button at the end of the page:

Step 8 Check that the new scope has been added under sensitive scopes:

Step 9 Click save and continue at the end of the page:

Stage 3: Create OAuth credentials

Step 1 Select credentials from the left-hand navigation menu:

Step 2 Click the create credentials button:

Step 3 Select OAuth client ID:

Step 4 Select web application:

Step 5 Enter a name for this application - we recommend something clearly identifiable as a Patchworks integration, for example Patchworks Web Client:

Step 6 Move down to the authorised redirect URIs section and click the add URI button:

Step 7 Enter the following URI:

https://developers.google.com/oauthplayground

Step 8 Click the create button:

Step 9 Your client ID and client secret are displayed - copy these and add them to your password manager so they're available in the next stage (and for later use in Patchworks):

Step 10 Click OK to close this window.

Stage 4: Apply credentials in the OAuth playground

Step 1 In a new browser tab/window, access the following URL to access the OAuth playground:

https://developers.google.com/oauthplayground

Step 2 In the top-right corner, click the 'cog' icon to access OAuth 2.0 configuration:

Step 3 At the end of the configuration page, select the use your own OAuth credentials checkbox:

Step 4 Add your client ID and client secret (created in the previous stage) into given fields:

Step 5 Close this window.

Stage 5: Obtain a refresh token

Step 1 Still in the OAuth playground, move to the end of the left panel and enter the following URL in the input your own scopes field:

https://www.googleapis.com/auth/spreadsheets

...then click the authorise APIs button:

Step 2 When prompted, log in with the same Google account that you started with in Stage 1:

...you should see confirmation that your app (in this case named Patchworks) has access to Google spreadsheets associated with this account:

Step 3 Click allow to continue to the OAuth 2.0 playground.

Step 4 Click the exchange authorization code for tokens button:

Step 5 Copy the refresh token and add it to your password manager.

Stage 6: Enable the Google Sheets API

Step 1 Switch back to your Google APIs console - APIs and Services tab/window and select enabled APIs and services from the left-hand navigation menu:

Step 2 Select enable APIs and Services at the top of the page:

Step 3 Search for Google sheets API:

Step 4 Click the Google sheets API result tile:

Step 5 Click the enable button:

Step 6 Google Sheets setup is now complete. If you haven't done so already, you can install the Google Sheets connector from the Patchworks marketplace and then use your client ID, client secret, and refresh token to add required connector instances.