Connectors
Connectors link Knots to external services. Each connector requires specific credentials or an OAuth authorization flow. Once created, a connector can be used across multiple workflows.
Amazon Selling Partner
Used for marketplace channel integration with Amazon Selling Partner.
Auth: Login with Amazon (LWA) — OAuth credentials
Required:
- Client ID
- Client Secret
- Refresh Token
- Region (Europe, North America, or Far East)
App Store Connect
Connect to Apple's App Store Connect API for app metadata, sales reports, and analytics.
Auth: API Key
Required:
- Issuer ID
- Key ID
- Private key (
.p8file contents)
AWS
Used as a ticket export destination — exports are written to an S3 bucket in your AWS account. Only S3 is supported.
Auth: IAM Role (no static credentials stored)
Required:
- IAM Role ARN (format:
arn:aws:iam::<account-id>:role/<role-name>) - External ID — generated automatically; must be set as a condition in your IAM trust policy
Azure AI Search
Used as a knowledge backend for AI integrations. Knots queries your Azure AI Search index to retrieve relevant context.
Auth: API Key
Required:
- Endpoint URL (your Azure AI Search service URL)
- API Key
- Index name
Optional:
- Vector field name
- Content field name
Azure OpenAI
Used to provide a custom AI model for your workspace. When configured, Knots uses your Azure-hosted deployment instead of the default Knots-provided model.
Auth: API Key
Required:
- Endpoint URL (your Azure resource URL)
- API Key
- Deployment/Model ID
Dropbox
Used as a ticket export destination — exports are written to your Dropbox.
Auth: OAuth — you will be redirected to Dropbox to authorize access after saving the connector name.
Required:
- Connector name (to start the OAuth flow)
eBay
Used for marketplace channel integration with eBay.
Auth: OAuth — you select the permission scopes, then authorize via eBay.
Required:
- Connector name
- Scopes — choose from available eBay API permission scopes (e.g. Orders, Inventory, Finances). Some public scopes are required and cannot be deselected.
Freshdesk
Connect to Freshdesk to read and manage tickets and contacts.
Auth: API Key
Required:
- Subdomain (your
<subdomain>.freshdesk.comidentifier) - API Key
FTP
Used as a ticket export destination — exports are written to your FTP server.
Auth: Username and password
Required:
- Host (hostname or IP)
- Username
- Password
- Port (default: 21)
Generic
Connect to any HTTP API with configurable authentication.
Auth: Choose one of:
- No auth
- Basic auth (username + password)
- API key
- OAuth token (client credentials or authorization code)
- Custom token (with configurable token endpoint and request format)
Required:
- Base URL
- Auth type and its corresponding credentials/settings
Used for two channel integrations:
- Google My Business — manage and respond to customer reviews
- Google Play Store — import and respond to app reviews
Auth: OAuth — you will be redirected to Google to authorize access after saving the connector name.
Required:
- Connector name (to start the OAuth flow)
Google Gmail
Connect to Gmail to read and send emails.
Auth: OAuth or Service Account
- OAuth: Client ID and Client Secret (from a Google Cloud project with Gmail API enabled)
- Service Account: Service account JSON key and subject email (the Gmail account to impersonate)
Google Sheets
Connect to Google Sheets to read and write spreadsheet data.
Auth: OAuth or Service Account
- OAuth: Client ID and Client Secret (from a Google Cloud project with Sheets API enabled)
- Service Account: Service account JSON key and subject email (the account to impersonate)
Jira
Connect to Jira to read and manage issues and projects.
Auth: OAuth — you will be redirected to Atlassian to authorize access.
Required:
- Subdomain (your
<subdomain>.atlassian.netidentifier)
OpenAI
Used to provide a custom AI model for your workspace. When configured, Knots uses your OpenAI account instead of the default Knots-provided model.
Auth: API Key
Required:
- API Key (from your OpenAI account)
PostgreSQL
Used for Studio integrations — connects Knots Studio to your PostgreSQL database.
Auth: Database credentials
Required:
- Host
- Port (default: 5432)
- Database name
- Username
- Password
SFTP
Used as a ticket export destination — exports are written to your SFTP server.
Auth: Username and password, or SSH private key
- Password: Username and password
- Private key: Username, private key (PEM format), and optional passphrase
Required:
- Host
- Port (default: 22)
SharePoint
Used as a ticket export destination — exports are written to your SharePoint site.
Auth: OAuth — you will be redirected to Microsoft to authorize access.
Required:
- Subdomain (your
<subdomain>.sharepoint.comidentifier)
Shopify
Connect to a Shopify store to read orders, products, customers, and more.
Auth: OAuth (app credentials)
Required:
- Store subdomain (your
<subdomain>.shopify.comstore) - Client ID
- Client Secret
Shopware
Connect to a Shopware 5 store to read and manage data.
Auth: Username and password
Required:
- Domain (your Shopware store URL)
- Username
- Password
Zendesk
Connect to Zendesk to read and manage tickets, users, and organizations.
Auth: OAuth — you will be redirected to Zendesk to authorize access.
Required:
- Subdomain (your
<subdomain>.zendesk.comidentifier)