OIC – Evernote Adapter

28 October, 2020 Daniel Teixeira Evernote 0

Update November 2020:

Well, it seems that right after this article, the Evernote Adapter reached its end-of-life: 

You cannot create new connections of the Evernote Adapter or Oracle Monetization Cloud Adapter. Existing connections of both adapters continue to work.

—————————————-

I started using Evernote some time ago, as a means to store my cooking recipes:) Up until then, every time I had to cook, I had to google for the recipes to help me remember the ingredients – over and over again – with Evernote I keep my own recipes at hand.

What does this have to do with Enterprise Integration you may ask? Well…nothing, but it triggered me to go and try the OIC Evernote Adapter.

According to the Documentation, it is meant for these type of use cases:

“For example, you can collect rich information about your customers, including notes, contact details, and other information into secure notes that only authorized team members can view in one place through Evernote. To collect contact information, use the Oracle Service Cloud (RightNow) Adapter.”

The API reference: https://dev.evernote.com/doc/reference/  

 
First step is to create a developer account with Evernote.
 

An important note from the Documentation:

“Activate the API Key in a Production Environment

Evernote has two environments: sandbox and production. Only the production environment is currently supported.

When an API key is requested from Evernote, the key provided by Evernote is initially active only in the sandbox environment. Therefore, when you try to create a connection instance using this key, the following error message is displayed:

Missing required oauth parameter "oauth_token"

To resolve this issue, you must follow the steps described at https://dev.evernote.com/support/glossary.php#k to activate your key in a production environment. Once the API key is active in a production environment, Evernote sends you an email confirming activation. After receiving this email, connection instances can be tested and used.”

NOTE: My original app name contained “Evernote” in the name, which is not allowed for production. After being renamed to Personal, they granted me access!

Create a Connection

The typical properties need to be filled, Name,Identifier and an optional Description.

The security parameters are the ClientId and Client Secret from Evernote.

You need to provide consent – and while doing so, Evernote clearly explains what is possible or not, with the Access Level (Basic) I have for the API.

And at the end you should see the Access Allowed message from OIC 🙂

 
Create an Integration
Create an AppDriven Integration that takes a REST Trigger and calls the Evernote adapter to create a note.
 
Drag a REST Trigger, with a POST action that has /note as the URI 
Add 3 parameters to the URI – Title,Author and Note – we will map these to the Evernote request.

At the end it should be similar to this.

This edition of the API is limited, but it’s enough for demo purposes. We choose the Operation Create Note.

The mapping is pretty straightforward.

Now we are ready to Activate and Test it!!

Activate and Test
With the new feature to test REST triggered Integrations from the console we don’t need POSTMAN anymore!
Fill in the parameters and press test.

Monitor and Verify Result

And as expected we see the note created in my Evernote account!
 

Easy, yet powerful!