You can authenticate with Microsoft to create your own instance of the Outlook Email element through the UI or through APIs. Once authenticated, you can use the element instance to access the different functionality offered by the Microsoft platform.
Use the UI to authenticate with Microsoft and create a Outlook Email element instance. Microsoft authentication follows the typical OAuth 2.0 framework and you will need to sign in to Microsoft as part of the process.
If you are configuring events, see the Events section.
To authenticate an element instance:
After successfully authenticating, we give you several options for next steps. Make requests using the API docs associated with the instance, map the instance to a virtual data resource, or use it in a formula template.
Authenticating through API is similar to authenticating via the UI. Instead of clicking and typing through a series of buttons, text boxes, and menus, you will instead send a request to our /instances
endpoint. The end result is the same, though: an authenticated element instance with a token and id.
Authenticating through API follows a multi-step OAuth 2.0 process that involves:
Use the following API call to request a redirect URL where the user can authenticate with the service provider. Replace {keyOrId}
with the element key, outlookemail
.
curl -X GET /elements/{keyOrId}/oauth/url?apiKey=<Microsoft Application Id>&apiSecret=<Microsoft Password/PublicKey> &callbackUrl=<Microsoft Redirect URL>&scope=offline_access https://outlook.office.com/mail.send https://outlook.office.com/mail.read https://outlook.office.com/mail.readwrite
Query Parameter | Description |
---|---|
apiKey | The API key or client ID obtained from registering your app with the provider. This is the Application Id that you recorded in API Provider Setup. |
apiSecret | The client secret obtained from registering your app with the API provider. This is the Password/PublicKey that you recorded in API Provider Setup. |
callbackUrl | The URL that the API provider returns a user to after they authorize access. This is the Redirect URL that you recorded in API Provider Setup |
scope | The list of scopes granted to the app. The list in the example (offline_access https://outlook.office.com/mail.send https://outlook.office.com/mail.read https://outlook.office.com/mail.readwrite ) represent the minimum required to make the requests in Outlook Email's element API docs. |
curl -X GET \
'https://api.cloud-elements.com/elements/api-v2/elements/outlookemail/oauth/url?apiKey=Rand0MAP1-key&apiSecret=fak3AP1-s3Cr3t&callbackUrl=https:%3A%2F%2Fwww.mycoolapp.com%2auth&scope=offline_access%20https://outlook.office.com/mail.send%20https://outlook.office.com/mail.read%20https://outlook.office.com/mail.readwrite' \
Use the oauthUrl
in the response to allow users to authenticate with the vendor.
{
"oauthUrl": "https://login.microsoftonline.com/common/oauth2/v2.0/authorize?scope=offline_access+https%3A%2F%2Foutlook.office.com%2Fmail.send+https%3A%2F%2Foutlook.office.com%2Fmail.read+https%3A%2F%2Foutlook.office.com%2Fmail.readwrite&response_type=code&redirect_uri=https%3A%2F%2Fhttpbin.org%2Fget&state=outlookemail&client_id=Rand0MAP1-key",
"element": "outlookemail"
}
Provide the oauthUrl
in the response from the previous step to the users. After users authenticate, Microsoft provides the following information in the response:
Response Parameter | Description |
---|---|
code | The authorization grant code returned from the API provider in an OAuth 2.0 authentication workflow. Cloud Elements uses the code to retrieve the OAuth access and refresh tokens from the endpoint. |
state | A customizable identifier, typically the element key (outlookemail ) . |
error
instead of the code
parameter. In this case, your application can handle the error gracefully.
Use the code
from the previous step and the /instances
endpoint to authenticate with Microsoft and create an element instance. If you are configuring events, see the Events section.
To authenticate an element instance:
Construct a JSON body as shown below (see Parameters):
{
"element": {
"key": "outlookemail"
},
"providerData": {
"code": "<AUTHORIZATION_GRANT_CODE>"
},
"configuration": {
"oauth.api.key": "<Microsoft app Application Id>",
"oauth.api.secret": "<Microsoft app Password/PublicKey>",
"oauth.callback.url": "<Microsoft app Redirect URL >"
},
"tags": [
"<Add_Your_Tag>"
],
"name": "<INSTANCE_NAME>"
}
Call the following, including the JSON body you constructed in the previous step:
POST /instances
Locate the token
and id
in the response and save them for all future requests using the element instance.
curl -X POST \
https://api.cloud-elements.com/elements/api-v2/instances \
-H 'authorization: User <USER_SECRET>, Organization <ORGANIZATION_SECRET>' \
-H 'content-type: application/json' \
-d '{
"element": {
"key": "outlookemail"
},
"providerData": {
"code": "xxxxxxxxxxxxxxxxxxxxxxx"
},
"configuration": {
"oauth.api.key": "Rand0MAP1-key",
"oauth.api.secret": "fak3AP1-s3Cr3t",
"oauth.callback.url": "https;//mycoolapp.com"
},
"tags": [
"Docs"
],
"name": "API Instance"
}'
API parameters in the UI are bold, while parameters available in the instances API are in code formatting
.
Parameter | Description | Data Type |
---|---|---|
key |
The element key. outlookemail |
string |
code |
The authorization grant code returned from the API provider in an OAuth 2.0 authentication workflow. Cloud Elements uses the code to retrieve the OAuth access and refresh tokens from the endpoint. | string |
Namename |
The name of the element instance created during authentication. | string |
oauth.api.key |
The API key or client ID obtained from registering your app with the provider. This is the Application Id that you noted in API Provider Setup. | string |
oauth.api.secret |
The client secret obtained from registering your app with the API provider. This is the Password/PublicKey that you noted in API Provider Setup. | string |
oauth.callback.url |
The URL that the API provider returns a user to after they authorize access. This is the Redirect URL that you noted in API Provider Setup. | string |
Tagstags |
Optional. User-defined tags to further identify the instance. | string |
In this example, the instance ID is 12345
and the instance token starts with "ABC/D...". The actual values returned to you will be unique: make sure you save them for future requests to this new instance.
{
"id": 12345,
"name": "Instance via API",
"createdDate": "2017-11-30T21:53:35Z",
"token": "ABC/D...xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"element": {
"id": 6410,
"name": "Outlook Email",
"key": "outlookemail",
"description": "Add an Outlook Email Instance to connect your existing Outlook account to the general Hub, allowing you to manage your emails across multiple general Elements.You will need your Outlook account information to add an instance ",
"image": "elements/custom-element-default-logo.png",
"logo": "outlookemail",
"active": true,
"deleted": false,
"typeOauth": false,
"trialAccount": false,
"resources": [ ],
"transformationsEnabled": true,
"bulkDownloadEnabled": true,
"bulkUploadEnabled": true,
"cloneable": true,
"extendable": true,
"beta": false,
"authentication": {
"type": "oauth2"
},
"extended": false,
"useModelsForMetadata": true,
"hub": "general",
"protocolType": "odata",
"parameters": [ ],
"private": false
},
"elementId": 6410,
"tags": [
"Docs"
],
"provisionInteractions": [],
"valid": true,
"disabled": false,
"maxCacheSize": 0,
"cacheTimeToLive": 0,
"providerData": {
"code": "xxxxxxxxxxxxxxxxxxxxxxxxxxx"
},
"configuration": { },
"eventsEnabled": false,
"traceLoggingEnabled": false,
"cachingEnabled": false,
"externalAuthentication": "none",
"user": {
"id": 123456,
"emailAddress": "claude.elements@cloud-elements.com",
"firstName": "Claude",
"lastName": "Elements"
}
}