Connector Classifications¶
Introduction¶
Connectors are documented individually but can be classified by their use:
-
API: Use the API connector in conjunction with a Jitterbit Custom API that is configured through the API Manager.
-
Short-term Storage: Use the Local Storage, Temporary Storage, or Variable connectors for temporary storage of files.
-
Long-term Storage: Use the File Share, FTP, or Database connectors for long-term or permanent storage of files.
-
Service-based: Use the HTTP or SOAP connectors for connecting to web services that don't already have an application connector or that you want to connect to using a standards-based web service.
-
Application: Use these connectors as the recommended way to connect to a specific application, such as NetSuite, Salesforce, ServiceNow, or Workday.
Connectors can also be differentiated by how their schemas are defined:
- Connector-generated Versus User-defined: These terms are used in addition to the classifications listed above to refer to connectors that provide a schema (connector-generated) versus those where you provide the schema yourself (user-defined).
Connector Use¶
These connector classifications are by the type of use of the connector.
API¶
Short-term Storage¶
Long-term Storage¶
Service-based¶
Note
A beta version of Jitterbit's HTTP v2 (Beta) connector (an application connector) is also available. For more information, see REST-based Connector Considerations.
Application¶
- Act! CRM *
- Active Directory *
- Acumatica *
- Adobe Analytics *
- ADP *
- Airtable *
- Algonomy Personalization
- Amazon Athena *
- Amazon Dynamo DB *
- Amazon Marketplace *
- Amazon Redshift
- Amazon S3
- Amazon SQS
- ANYMARKET
- Apache Cassandra *
- Apache Kafka
- Authorize.net *
- Azure Data Catalog *
- Azure Data Lake Storage *
- Basecamp *
- BigCommerce
- Blackbaud Raiser’s Edge NXT *
- BMC Helix Business Workflows
- BMC Helix for CSP
- BMC Helix ITSM
- BMC Helix Operations Management
- Box
- Bullhorn CRM *
- Cherwell
- Cloud Firestore
- Constant Contact
- Correios
- Couchbase *
- Coupa
- DocuSign
- Dynamics 365 Business Central *
- Dynamics 365 Finance and Operations *
- Dynamics 365 Sales *
- Dynamics GP *
- eBay *
- EDI for Cloud
- Elasticsearch
- Epay
- Epicor Kinetic
- Epicor Prophet 21
- Evernote
- Exact Online *
- Financial Edge NXT *
- GitHub
- Google Ad Manager *
- Google Ads*
- Google Cloud Storage *
- Google Data Catalog *
- Google Docs
- Google Drive
- Google Pub Sub
- Google Sheets
- GraphQL *
- Gzip
- HTTP v2 (Beta)
- HubSpot
- Intelipost
- Jenkins
- Jira
- Jitterbit App Builder
- Jitterbit MQ (Beta)
- JMS
- LDAP
- Linio
- Magazine Luiza Companies
- Magazine Luiza Shopping
- Magento
- Marketo *
- Microsoft Advertising *
- Microsoft Azure Table Storage *
- Microsoft Dataverse *
- Microsoft Dynamics AX *
- Microsoft Dynamics CRM *
- Microsoft Excel *
- Microsoft Excel Online *
- Microsoft Exchange *
- Microsoft Office 365 *
- Microsoft OneDrive *
- Microsoft SSAS *
- Microsoft Teams
- Mirakl
- MongoDB
- MS Azure AD
- MYOB *
- NetSuite
- OData
- Oracle Commerce Cloud
- Oracle Eloqua *
- Oracle Sales Cloud *
- PagerDuty
- Quickbooks Point of Sale *
- RabbitMQ
- Reckon Accounts Hosted *
- Ripley
- Sage 50 UK *
- Sage 200 *
- Sage 300 *
- Sage Business Cloud Accounting *
- Sage Intacct *
- Salesforce
- Salesforce Einstein Analytics
- Salesforce Events (Beta)
- Salesforce Marketing Cloud *
- Salesforce Pardot *
- Salesforce Service Cloud
- SAP
- SAP BusinessObjects BI *
- SAP Business ByDesign *
- SAP Business One *
- SAP Concur
- SAP Fieldglass *
- SAP Gateway *
- SAP HANA XS Advanced *
- SAP Hybris C4C *
- SendGrid
- ServiceMax
- ServiceNow
- ShipStation
- Shopify
- Slack
- Smartsheet
- SMB
- Snowflake
- Square
- Stripe
- SugarCRM
- SuiteCRM *
- Via B2B
- VTEX
- WhatsApp Business
- WooCommerce
- Workday
- Workday Prism Analytics
- Xero *
- YAMI
- Zendesk
Note
Application connectors listed above in italics and with an asterisk (such as Active Directory *) can be used only with Private Agents.
In addition, these connectors are application connectors:
- Custom connectors created with Connector Builder
- Custom connectors created with the Connector SDK
Additional application-specific connectors are being added with each new Harmony release and are updated here over time.
Connector Schema Definition¶
In addition to the above connector classifications by use, connectors can also be referred to based on how their schemas are defined.
Connector-generated Versus User-defined¶
Connectors can have schemas that are connector-generated or user-defined.
For information about schema caching and refreshing for both connector-generated and user-defined schemas, see Schema Regeneration.
Connector-generated¶
Connector-generated schemas are defined in an activity and are either fixed in the connector or are generated directly from the endpoint. Connector-generated schemas have an automatically generated name that depends on whether the schema is a request or response:
User-Defined Endpoint Name→User-Defined Activity Name→Request
User-Defined Endpoint Name→User-Defined Activity Name→Response
This transformation shows the names of connector-generated schemas being inherited from activities on both its source and target sides:
Depending on the connector, the structure of some connector-generated schemas may be edited by the user, or the structure may dynamically change based on user input provided during activity configuration or based on changes in the endpoint itself.
The names of connector-generated schemas cannot be edited by a user.
User-defined¶
A user-defined schema is provided by the user, either by creating a custom schema, by uploading a file or URL, or by manually entering the schema. User-defined schemas can be defined in certain activities or defined in a transformation.
The names of user-defined schemas are based on the name of the provided file or are user-defined.