Skip to Content

Evernote Connector

Summary

The Jitterbit Harmony Evernote Connector establishes access to Evernote.

The Evernote connector provides an interface for creating an Evernote connection, the foundation used for generating instances of Evernote activities. These activities, once configured, interact with Evernote through the connection.

The Evernote connector is accessed from the design component palette's Connections tab (see Design Component Palette).

Connector Overview

This connector is used to first configure an Evernote connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific Evernote connection and its activities are referred to as an Evernote endpoint:

Evernote activity types

  • Create Notes: Creates notes in Evernote and is intended to be used as a target in an operation.

  • Delete Notes: Deletes notes from Evernote and is intended to be used as a target in an operation.

  • Get Notes: Retrieves notes from Evernote and is intended to be used as a source in an operation.

  • Update Notes: Updates notes in Evernote and is intended to be used as a target in an operation.

Note

This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Prerequisites and Supported API Versions

The Evernote connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

The Evernote connector uses the Evernote Cloud API. Refer to the API documentation and Evernote's Data Model for information on the schema nodes and fields.

Troubleshooting

If you experience issues with the Evernote connector, these troubleshooting steps are recommended:

  1. Ensure the Evernote connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.

  4. If using Private Agents, you can check the agent logs for more information.