-
Support March 24th, 2026 @ 7:09 pm
Happy to help.
In Step 1: The PHP script itself will need to be hosted on a server that is reachable from Mailchimp. And yes, the $sugar_url will contain the local address of the CRM. So here, the
$sugar_urlshould be set:http://10.10.0.1/index.php.In Step 2: In Mailchimp, for each list that syncs to your CRM, you will configure a webhook URL that points to the public URL of the PHP script in step 1. The full webhook URL will look something like:
https://our.dmz.server.tld/script.php?module=SugarChimp&entryPoint=SugarChimpWebhookThe steps to create the webhook can be found here: https://mailchimp.com/developer/marketing/guides/sync-audience-data-webhooks/#create-a-new-webhook. You'll want to add a webhook for each of the lists you're syncing.
In Step 3, reverse proxy does refer to the same public script mentioned. This is acting as the proxy between Mailchimp and your CRM. Updating this tells SugarChimp that webhook traffic is coming through that proxy URL so it can handle the requests properly. So in the query example,
https://your-CRM-endpointshould be the base URL of that proxy script, without the query string. Using your example:• Mailchimp webhook would look like (this points to the server that is accessible to the public):
https://our.dmz.server.tld/script.php?module=SugarChimp&entryPoint=SugarChimpWebhook•reverse_proxyconfig value in the database would be:https://our.dmz.server.tld/script.phpFor this step, prior to running the query, you'll want to first see if you have the reverse_proxy config. If you do, you can just update the config to the value above. If you don't, you'll want to use the INSERT query in the support article.
Once that is set up, you should see campaign activity for new campaigns sync back to the CRM.
Best, Heidi
View Comment
-
Support March 23rd, 2026 @ 4:55 pm
Thanks for the message. It sounds like you've correctly identified the issue. Since your CRM is on-premise and only accessible via VPN, Mailchimp's webhooks can't reach it. A reverse proxy, using the code snippet from the article, is still the right solution here as it is a publicly accessible server that receives Mailchimp's webhook data and forwards it internally to your CRM instance. Suite 7.15 does include proxy settings under System Settings, but it looks like this setting controls outbound traffic and won't replace the need for this process. Those steps are still required for Mailchimp to send data back into Sugar.
Your network admin will need to:
- Deploy the proxy script. Place the PHP proxy script (from the article) on a publicly accessible web server. This cannot be the CRM server itself, since it must be reachable from the internet. In the script, update $sugar_url to your CRM's internal address.
- Update your Mailchimp webhooks. For each synced Mailchimp audience, update the webhook URL to point to your new public proxy script. The format for the webhook is also provided in the article referenced.
- Update the 'reverse_proxy' config in your CRM's database. This will tell SugarChimp to route Mailchimp webhook traffic through the proxy to reach your CRM.
You should be able to get this working now using the http:// + your current subdomain temporarily. Once your internal HTTPS subdomain is live and publicly accessible, you can update the $sugar_url value in the proxy script to use that URL instead.
Let me know if you have any trouble along the way.
Best, Heidi
View Comment
-
Support March 23rd, 2026 @ 4:54 pm
Thanks for the message. It sounds like you've correctly identified the issue. Since your CRM is on-premise and only accessible via VPN, Mailchimp's webhooks can't reach it. A reverse proxy, using the code snippet from the article, is still the right solution here as it is a publicly accessible server that receives Mailchimp's webhook data and forwards it internally to your CRM instance. Suite 7.15 does include proxy settings under System Settings, but it looks like this setting controls outbound traffic and won't replace the need for this process. Those steps are still required for Mailchimp to send data back into Sugar.
Your network admin will need to: -Deploy the proxy script. Place the PHP proxy script (from the article) on a publicly accessible web server. This cannot be the CRM server itself, since it must be reachable from the internet. In the script, update $sugar_url to your CRM's internal address. -Update your Mailchimp webhooks. For each synced Mailchimp audience, update the webhook URL to point to your new public proxy script. The format for the webhook is also provided in the article referenced. -Update the 'reverse_proxy' config in your CRM's database. This will tell SugarChimp to route Mailchimp webhook traffic through the proxy to reach your CRM.
You should be able to get this working now using the http:// + your current subdomain temporarily. Once your internal HTTPS subdomain is live and publicly accessible, you can update the $sugar_url value in the proxy script to use that URL instead.
Let me know if you have any trouble along the way.
View Comment
-
Support March 23rd, 2026 @ 4:52 pm
Thanks for this insight. We did check with SuiteCRM and are working with them on a solution for going forward. I'll close this out for now.
View Comment
-
Support March 18th, 2026 @ 7:53 pm
Just wanted to loop back up with you. I don't yet have more information, but I did want to let you know our team is still looking into this issue.
Heidi
View Comment
-
Support March 17th, 2026 @ 3:26 am
Thanks for reaching out and sharing this experience; happy to help. I'm taking a closer look and will follow up again shortly!
Best, Heidi
View Comment
-
Support June 18th, 2025 @ 6:36 pm
Hi Nathan,
View Comment
Thanks for sending this along. Just to confirm, are you attempting to install FanaticalZendesk-2.9.12-for-SuiteCRM.zip (the latest version that's on The SuiteCRM Store)?
This issue might be related to file permissions on the server. Do you know what your permissions are set as? Here's Suite recommended guidance: https://docs.suitecrm.com/admin/installation-guide/downloading-installing/#_copying_suitecrm_files_to_web_server
It also might be worth checking your group and user ownership.
For temporary testing purposes, can you try opening those permissions up to 777 and trying the install again to see if the same error appears?
Heidi
-
Support June 17th, 2025 @ 9:37 pm
Hi Nathan,
View Comment
Happy to help. Can you tell me the version of Suite or Sugar you're installing into? As well as the version of Fanatically Zen that you're attempting to install?
Thanks for your help in troubleshooting!
Best, Heidi
-
Support January 24th, 2025 @ 7:23 pm
Apologies for the delay here. Fanatically Zen is expected to work with Suite 8+, though some features may have limited functionality. If you encounter difficulties, please let us know.
Best, Heidi
View Comment
-
Support January 6th, 2025 @ 9:07 pm
Apologies for the delay! We’re currently reviewing compatibility with SuiteCRM 8.6 to ensure everything works seamlessly. I’ll keep you updated as soon as I have a definitive answer.
Can you tell me if you're looking to just view data (see Suite data in Zendesk and Zendesk data in Suite) or are you also looking to sync data from Zendesk to Suite?
Thanks, Heidi
View Comment
-
Support August 20th, 2024 @ 1:28 pm
Glad to hear! Please let us know if you encounter any further trouble as you continue your work with SugarChimp.
View Comment
-
Support February 19th, 2024 @ 6:14 pm
If we do build something that would work for your purposes in the future, I'll loop back here and let you know. Thanks for taking a look at Glances and if you need us in the meantime, we're here!
Best, Heidi
View Comment
-
Support February 16th, 2024 @ 6:08 pm
Happy to help, Dwayne! Thanks for considering Glances and we appreciate your thoughts on the SuiteCRM and QuickBooks work we've done!
Glances has a feature we call Actions, which allows you to complete tasks across apps. You can see more about this feature here: https://glances.com/actions. It's worth noting that this Actions feature isn't an automated integration. Instead, it's an extension of your workflow so you can manually take action when needed. If you need something to monitor QuickBooks for PAID statuses and trigger a workflow on its own, Glances won't be the right fit.
If, however, you need to manually complete something when you see a PAID status, Glances might be able to work. For example, if you're reviewing paid invoices in QuickBooks and want to quickly create a case or a task within Suite without navigating away, that's something Glances could accommodate.
If that's the kind of solution you're looking for, feel free to schedule a quick chat here: https://calendly.com/glances/glances-consultation. We'll use this time to show you a little about Glances and learn more about the workflow you're looking to accomplish.
Let me know if you have any other questions!
Best, Heidi
View Comment
-
Support April 6th, 2023 @ 6:12 pm
Happy to help. We would expect that when a record is marked as opted out in Suite that would sync to Mailchimp and mark them as unsubscribed. Can you tell me if other changes (such as someone changing a contact's name) is syncing to Mailchimp as expected or does it seem like just unsubscribes aren't syncing?
Can you also send along a screenshot of the Health Status page (from the top to the bottom of the lists that are syncing)? You can access this by navigating to the Admin page and clicking on Health Status under the SugarChimp section. Additionally, can you send a copy of your CRM logs as well? For privacy purposes, you can email both of those to mailchimp@fanaticallabs.com. Steps for the logs are below:
- From within Admin click System Settings
- Click View Log at the bottom of the page
- Click All at the top of the page
- Copy/paste the text that appears into a .txt file and send it along
Thanks, Heidi
View Comment
-
-
-
-
-
Fanatical Labs has not rated any add-ons.
Fanatical Labs has not verified any add-ons.
Fanatical Labs has not created any Wanted Add-ons.