Re: [Architecture] Choosing APIs for implementing connectors

2017-07-27 Thread kausik .M
Hi all, In this use cases we are planning :- 1.From the twitter connector we are getting retrieve searches and also from the CallRail connector we are Retrieving caller contact details then from our *Followupboss* connector we are creating leads from those details. And also from the

Re: [Architecture] Choosing APIs for implementing connectors

2017-07-10 Thread kausik .M
On Mon, Jul 10, 2017 at 10:55 PM, kausik .M <kausik...@gmail.com> wrote: > Hi all, > > We changed 2 APIs because it doesn't allow the trial version to get API > access. > We changed > 1.Sage > 2.Dotmailer > > For that we choosed > 1.amoCRM - amoCRM is a very

Re: [Architecture] Choosing APIs for implementing connectors

2017-07-10 Thread kausik .M
Hi all, We changed 2 APIs because it doesn't allow the trial version to get API access. We changed 1.Sage 2.Dotmailer For that we choosed 1.amoCRM - amoCRM is a very friendly CRM and B2B leads and sales management solution. The vendor won our *Expert’s Choice Award for 2017* as well as the