Cardin for Outlook
Cardin for Outlook can connect to multiple cloud apps (e.g. CRM, accounting, etc.) at the same time and display matching results from each app simultaneously. We built this initially to prove out our Gmail CardService emulation library for Outlook. It also helps power users easily handle multiple cloud apps or multiple accounts within the same cloud app. This add-on is free to use.
Choose between Connector types that we created to help you bring all the info you need to your inbox by connecting to popular tools ranging from CRM systems to powerful workflow products such as Microsoft Flow allowing you to add any cloud app you want (we are constantly expanding, so be sure to subscribe to stay notified):
Contextually access contacts from 1CRM all-in-one platform and keep track of your pending activities for the upcoming week directly from your inbox!
Sync contact and company info and get pipeline reports from simple CRM tailored for small businesses and make it even less annoying by staying in your inbox (contact add & edit features included)!
Directly access your Pipedrive account – whether you want to see detailed contact info or assigned deals and activities without leaving your inbox – our Pipedrive Connector is the right tool for the job!
Connect to any cloud app you can think of, be it QuickBooks, MailChimp, Trello, Gmail and much more – and have all of them at your fingertips at the same time while you traverse your daily mail with the Webhook Connector!
Creating a Connector is as simple as choosing what type you want to use and filling out the required configuration fields. In most cases, you only need to edit a Connector name to be able to identify it easily (you can leave everything as is, of course, and make changes later), but some Connectors require a more sophisticated configuration – do not worry, you will be guided through each step of the process and if you still encounter difficulties, you can always ask us for help or refer to our comprehensive tutorials
Each Connector type has general settings that allow you to set its basic configuration and behaviour and additional settings specific to the type you chose:
Connector display name
Every Connector type requires new instances to be named. By default, it is set to the Connector’s type name, but can be anything you want it to be (just remember that if you try to save an unnamed one, it will be created with default name)
Some Connectors can be configured to perform different actions, such as searching contact info or creating pipeline reports. You can create multiple instances of the same type performing different actions
Free tiers of most workflow tools like Flow have quota limits on how many times an integration can be run per month – understanding these limitations led us to the idea of giving you a choice to set up your Connectors as manual to only run when explicitly invoked:
You can check at a glance whether the Connector is manual or automatic and if the currently open email was matched by one of the Connectors set to auto or if any of them was misconfigured:
If you have a favourite Connector or just want to get straight to the point without choosing which Connector to open each time – just set it to be the default one – and it will be run every time you open a new email or refresh the Add-on:
Note that a list of available Connectors will be appended to the bottom of the display card under «Other connectors» section.
If you ever get tired of the Connector constantly being shown or change your mind, you can switch it off anytime by going to the settings card!
Many Connector types require additional setup to work correctly or provide optional features (e.g. pipeline Ids for LessAnnoying CRM).
If you choose such a Connector, you will be prompted to fill out additional fields (but do not worry – the Add-on will promptly explain each step necessary)
After you finish setting up a Connector, it will appear in the list of configured Connectors at the top of settings card – clicking on one of them will open a new card with the current Connector settings and an ability to update, authorize or remove it.
You can find instructions on less obvious steps of managing existing Connectors below:
If you do not like how the Connector list looks like (by default newer Connectors are pushed to the bottom of the list), you can set your own order!
Go to advanced settings section and choose between one of three ordering types and if the list should be displayed in reverse:
By creation time
You can remove any Connector by simply clicking on «remove» button in its settings card. As this is a sensitive action that can be triggered accidentally, you will be shown a confirmation card to make sure you really want to delete it:
And finally, if your Connectors list ever becomes unmanageable or you would like to start fresh – just open the advanced settings section and perform a full reset:
Please, note that doing so will wipe any Connectors that you currently have as well as any preferences you might have set for the Add-on without any possibility of restoration!
But do not worry, you will be asked to confirm this action:
In case the Add-in ever encounters an error that cannot be resolved by built-in error handling, it will display a user-friendly message that will help you troubleshoot if the issue is easy to solve (do not hesitate to contact us if you need assistance)
Most common error causes are:
Sometimes data source location you are trying to access changes or becomes otherwise unavailable (e.g. when you remove a Flow) – the Add-in will display an appropriate message to notify you and provide an opportunity to check the URL at a glance:
In case of any third-party service your Connector depends on becoming unavailable, a prompt describing failure reason will be shown (please, note that while we aim to help you as much as possible, our ability to display relevant prompts depend on the service in question):
Connecting to restricted APIs
Sometimes an external API you add as a Connector endpoint will require you to authorize to it with your user credentials (you can do this at any point in time from the Connector settings screen)
Currently we support API token authorization type for the Outlook Add-in and will add OAuth 2.0 flow in the near future – please, let us know if you want another type to be added – we will gladly do it in the next update!
APi token-based authorization flow is used by some of the endpoint applications for its simplicity and improved security over client credentials exchange (login and password) – in general, you have to obtain an API token from the endpoint resource to authorize it
To ensure that the process is easy for you, we provide a direct link and clear instructions on how to get the token for each Connector that requires API token authorization – just copy & paste it to authorization section input!