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 amoCRM API allows users to retrieve, search, edit and add contacts, deals, notes, and tasks. The service is available over HTTPS GET and POST calls, and returns XML for all responses. The software was developed deliberately to transform first-time contacts into leads, and to help you maintain an organized database and make better sales decisions. What this software also does is track your performance, so that you will always have the whole picture of your progress, and maximize the potential of your agents. It’s a cloud-based solution, so there is no need to download or install anything directly on your computer. These are the Methods i am planning to implement 1. GET accounts details of the CRM's user 2. POST contact - creating a contact 3. GET contact list - getting contact details list 4. GET contact links -getting contact details list's links 5. POST leads - creating a new contact 6. GET leads list - getting leads details list 7. GET leads links - getting leads details list 8. POST company - creating a company details 9. GET company list - getting companies details 10. POST customers - creating a customer details 11. GET customers list - getting the customer deatails 12. . POST transaction - creating the transaction details 13. GET transactions list - getting the transactions lists 14. GET transactions links - getting the transactions links details 15. POST tasks - creating a new task 16. GET tasks list - getting the all the tasks that is stored in the CRM 17. POST notes(events)- creating a new event 18. GET notes(events) - getting the current and future events 19. POST catalogs - creating a new catalog 20. GET catalogs - getting all the catalog details 21. POST links - creating a new link 22. GET links - getting the links details 23. POST fields - creating a new field 24. GET fields - getting the all the existing fields 25. POST pipelines - creating a new pipelines 26. GET pipelines - getting the all the pipelines details We can integrate amoCRM with some other applications also 1. https://www.getapp.com/customer-management-software/a/amocrm/integrations/ 2. https://zapier.com/zapbook/amocrm/ Thank You M.Kausik Computer Science University of Jaffna On Mon, Jul 10, 2017 at 10:55 PM, kausik .M <[email protected]> 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 friendly CRM and B2B leads and sales > management solution. The vendor won our *Expert’s Choice Award for 2017* as > well as the *Great User Experience Award*. > > The software was developed deliberately to transform first-time contacts > into leads, and to help you maintain an organized database and make better > sales decisions. What this software also does is track your performance, so > that you will always have the whole picture of your progress, and maximize > the potential of your agents. It’s a cloud-based solution, so there is no > need to download or install anything directly on your computer. > 2.wealthbox CRM > Weathbox is a web-and-mobile CRM application for financial professionals. > Version 1.0 of Wealthbox for financial advisors was launched on February > 11, 2014. New features and editions of Wealthbox in financial services are > in development now. Wealthbox is easy to use offering > getup-and-go-simplicity. No training required. Wealthbox allows users to > share CRM activity with staff to stay in the loop and get work done while > engaging with prospects. > > in next reply we all will describe our API's induvidualy > > Thank You > M.Kausik > Computer Science > University of Jaffna > > On Wed, Jul 5, 2017 at 9:40 AM, Malaka Silva <[email protected]> wrote: > >> 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] https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+Connector >> [2] https://docs.wso2.com/display/ESBCONNECTORS/Sample+Business+Scenarios >> >> On Tue, Jul 4, 2017 at 9:58 PM, Kausik <[email protected]> wrote: >> >>> 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-tp14 >>> 9953p149984.html >>> Sent from the WSO2 Architecture mailing list archive at Nabble.com. >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >> >> >> >> -- >> >> Best Regards, >> >> Malaka Silva >> Associate Director / Architect >> M: +94 777 219 791 <+94%2077%20721%209791> >> Tel : 94 11 214 5345 >> Fax :94 11 2145300 >> Skype : malaka.sampath.silva >> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >> Blog : http://mrmalakasilva.blogspot.com/ >> >> WSO2, Inc. >> lean . enterprise . middleware >> https://wso2.com/signature >> http://www.wso2.com/about/team/malaka-silva/ >> <http://wso2.com/about/team/malaka-silva/> >> https://store.wso2.com/store/ >> >> Don't make Trees rare, we should keep them with care >> > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
