Frequent disconnection with Zapier

Hi Omar - 

For myself, I've tried Zapier integrated with Sugar before and it has worked. One thing that's a best practice is to make sure you're using a dedicated user for the integration. If you log in using same username and password that Zapier uses then you can cause a login conflict that could cause you to bump the integration out of the system or vice versa.

My team supports software vendors that integrate with Sugar (ISV partnerships). If you could refer Zapier to us or add developers@sugarcrm.com to any active communication you have with Zapier then we can assist them in resolving this issue. Since their connection to Sugar was built and maintained by Zapier we don't have much to go on what could be wrong until we get information from them.

Maybe Sugar should implement a system for integrations that doesn't involve stealing from their users. Requiring users to pay for an additional license for every 3rd party integration they use is downright thievery.

Hi Avi Orzech ,

Technically speaking, Sugar prevents multiple users sessions on the same platform - which makes sense from a licensing perspective. If you don't want to use a dedicated license (or just want to dedicate a single license) for your various integrations, all you have to do is create a custom platform and specify that platform when requesting the authentication token.

These links explain in a little more detail:

https://support.sugarcrm.com/documentation/sugar_developer/sugar_developer_guide_13.1/integration/web_services/rest_api/#Authentication

https://support.sugarcrm.com/documentation/sugar_developer/sugar_developer_guide_13.1/integration/web_services/rest_api/#Avoiding_Login_Conflicts

Hope this helps.

I'm a user not a developer. It's not for me to fix Sugar's design faults.

Hi Avi Orzech ,

I understand your frustration. I'm just trying to help guide the issue here. If you have to use a dedicated user license for your third party integrations, the problem is most likely with the 3rd party integrating with Sugar's APIs rather than a design issue with Sugar itself.

Thank you for the info and concern. We have multiple integrations and therefore unable to use a specific user for each one. Running v11 on our own servers didn't seem to have the above issue. Since we moved to 13 in the cloud we're "suffering" for something Sugar should have fixed years ago.

Thank you for the info and concern. We have multiple integrations and therefore unable to use a specific user for each one. Running v11 on our own servers didn't seem to have the above issue. Since we moved to 13 in the cloud we're "suffering" for something Sugar should have fixed years ago.

Hi Avi Orzech ,

The authentication behaviors should largely be the same between v11 and v13 but things do happen sometimes. If you're interested, I'd be happy to connect and learn more about the issues you're having - I'm certain we can help remediate your concerns with v13 and SugarCloud.