Re: [Architecture] Choosing APIs for implementing connectors

Hi Kausik, Thx for the explanation. Looks good. On Fri, Jul 28, 2017 at 12:05 AM, kausik .M wrote: > 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

Re: [Architecture] Choosing APIs for implementing connectors

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

Hi all I'm also a member of kausik's group under 3rd year rapid application group project. I'm planning to do a connector for Buffer API. The following are methods which i have selected to implement. Buffer is a new and smarter way to share what you want to share on Social Media. People have

Re: [Architecture] Choosing APIs for implementing connectors

Hi all I am also a member of kausik's group under 3rd year rapid application group project. I am planning to to do a connector for FollowUpBoss API. Follow Up Boss is designed for real estate teams. Their mission is to help agents follow up faster, more often, and with the leads most likely to

Re: [Architecture] Choosing APIs for implementing connectors

Hi all I am also a member of kausik's group under 3rd year rapid application group project.I am planning to do a connector for StreakCRM API.Streak is the developer of an eponymous customer relationship management platform for Gmail.The following are methods which i have selected to implement.

Re: [Architecture] Choosing APIs for implementing connectors

Hi all I am also a member of kausik's group under 3rd year rapid application group project.I am planning to do a connector for StreakCRM API.Streak is the developer of an eponymous customer relationship management platform for Gmail.The following are methods which i have selected to implement.

Re: [Architecture] Choosing APIs for implementing connectors

Hi all I'm also a member of kausik's group under 3rd year rapid application group project. I'm planning to do a connector for wealthboxcrm API. The following are methods which i have selected to implement. I am going to implement wealthboxcrm. wealthboxcrm is, Weathbox is a web-and-mobile CRM

Re: [Architecture] Choosing APIs for implementing connectors

Hi all I'm also a member of kausik's group under 3rd year rapid application group project. I'm planning to do a connector for wealthboxcrm API. The following are methods which i have selected to implement. I am going to implement wealthboxcrm. wealthboxcrm is, Weathbox is a web-and-mobile

Re: [Architecture] Choosing APIs for implementing connectors

Hi all I'm also a member of kausik's group under 3rd year rapid application group project. I'm planning to do a connector for wealthboxcrm API. The following are methods which i have selected to implement. I am going to implement wealthboxcrm. wealthboxcrm is, Weathbox is a web-and-mobile

Re: [Architecture] Choosing APIs for implementing connectors

Hi all I'm also a member of kausik's group under 3rd year rapid application group project. I'm planning to do a connector for wealthboxcrm API. The following are methods which i have selected to implement. I am going to implement wealthboxcrm. wealthboxcrm is, Weathbox is a web-and-mobile

Re: [Architecture] Choosing APIs for implementing connectors

Hi all I'm also a member of kausik's group under 3rd year rapid application group project. I'm planning to do a connector for wealthboxcrm API. The following are methods which i have selected to implement. I am going to implement wealthboxcrm. wealthboxcrm is, Weathbox is a web-and-mobile CRM

Re: [Architecture] Choosing APIs for implementing connectors

Hi, I am Kausik.I am planning to implement amoCRM API's connector for our group. It is one the API from the 5 APIs in our group. This is the description of amoCRM Amo CRM amoCRM is an online sales and relationship management service designed to help users manage and pursue sales leads. The

Re: [Architecture] Choosing APIs for implementing connectors

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

Re: [Architecture] Choosing APIs for implementing connectors

-- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Choosing-APIs-for-implementing-connectors-tp149953p150157.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___ Architecture mailing list

Re: [Architecture] Choosing APIs for implementing connectors

Hi Kausik and Team, Good to hear. I think first you can share us the use case you are planning to implement. Then you can implement the connectors to support the mentioned use case. Find more details on samples and how to write a connector in [1] and [2] [1]

Re: [Architecture] Choosing APIs for implementing connectors

Thank You for your response. our group has 5 members. We are planning to do one connector per each person. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Choosing-APIs-for-implementing-connectors-tp149953p149984.html Sent from the WSO2 Architecture mailing list

Re: [Architecture] Choosing APIs for implementing connectors

Thank You for your response. our group has 5 members. We are planning to do one connector per each person. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Choosing-APIs-for-implementing-connectors-tp149953p149983.html Sent from the WSO2 Architecture mailing list

Re: [Architecture] Choosing APIs for implementing connectors

Thank you for your response. -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Choosing-APIs-for-implementing-connectors-tp149953p149967.html Sent from the WSO2 Architecture mailing list archive at Nabble.com. ___

Re: [Architecture] Choosing APIs for implementing connectors

Hi Kausik, Good to hear that you are interested in doing connectors. Yes I guess you have a good combinations of apis. CRM, Accounting, Marketing and social media. I guess you can come up with an interesting bossiness use case :) On Mon, Jul 3, 2017 at 8:59 PM, Kausik

[Architecture] Choosing APIs for implementing connectors

Hi All, We are planning to implement WSO2 ESB connectors for following APIs 1.Dotmailer 2.Sage 3.Streak 4.Buffer 5.Followupboss as a part of the 3rd year project for the course unit "Rapid Application Development". And also we will build a business scenario using these APIs. Can