Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hey everyone,

We desperately need some help because we’ve been stuck on this for almost four weeks now, and time is running out. Our team is trying to automate the transfer of contacts from Blinq to GoHighLevel (GHL) using Zapier, but we keep hitting roadblocks.

To make things even more fun (read: stressful), we’re completely new to automation - no formal training, no prior experience, just a whole lot of trial and error. And right now, it's mostly error. 😵‍💫 Our boss wants us to figure this out on our own, and while we’re learning, we’re also completely stuck.

What We've Tried

  • Set up a Zap with Blinq as the trigger and GHL as the action - no luck.

  • Looked into whether Blinq even integrates natively with Zapier (seems limited?).

  • Tried using webhooks to pull contact info from Blinq and push it into GHL.

  • Tried Make (formerly Integromat), but that failed too - it was even more complicated.

  • Ironically, we’ve had "successful" test runs where Zapier says everything worked, and the contact shows up in GHL... but in real-world use, actual contacts from Blinq aren’t making it into GHL. 🤯

Where It’s All Falling Apart

  • Zapier doesn’t seem to recognize new contacts from Blinq.

  • Webhook solutions aren’t triggering reliably (or at all).

  • The data isn’t actually transferring from Blinq to GoHighLevel, even though test runs say it should be working.

What We Need Help With

If anyone out there has successfully automated Blinq → GoHighLevel, please send help.

  • Are we missing something obvious?

  • Is Zapier even the best tool for this, or should we try something else?

  • If Zapier is the right way, how do we actually make it work with Blinq?

  • Should we be using a different trigger/method for Blinq?

  • Any debugging tips? If the Zap runs but doesn’t send data, where should we look?

This is getting urgent, and our boss isn’t going to stay patient much longer. We’d appreciate any guidance, advice, or even just moral support at this point.

Thanks in advance!

----
Screenshots here:

 

 

 

 

 

Hi ​@nb34,

 

Welcome to the Community.

 

If your Zap isn’t working as expected, double-check the trigger setup, ensuring new contact data in Blinq is added and polling is frequent enough. For webhooks, ensure Blinq’s webhook is appropriately configured and that data is being sent correctly. Check that the data mapping to GoHighLevel (GHL) fields is accurate and matches the formats. Use Zapier’s Task History and test more straightforward data to isolate issues. If the problem persists, consider exploring other tools like Integromat/Make or a custom API integration.

 

I hope this helps. Let us know if you need further assistance.

Thaaaaanks! We’ll try your suggestions. Meanwhile, why does this keep turning off on its own even though we published it?

 

Hi ​@nb34,

 

If your Zap is turning off automatically, it could be due to repeated errors, billing issues, plan limits, or API restrictions from connected apps. Check your Zapier notifications for error details, ensure your billing is up to date, and verify if you've exceeded task or API limits.

The account is paid.. We’ve also tried redoing from scratch: same results - successful tests, no actual Blinq contacts going through in GHL/Lead Connector still. Are you able to troubleshoot, please? Thanks!

Hi there, ​@nb34! 👋

Sorry to hear of all the trouble you’ve been having with this Zap. From your screenshots it looks as though both the Blinq trigger and LeadConnector action are set up correctly, especially as the tests are going through successfully. Neither of those apps are premium apps, and there’s only one action in the Zap so wouldn’t require a paid Zapier plan. If there’s no errored runs in the Zap history as it’s not triggering or is being switched off before it has a chance to trigger, then my guess would be that the Blinq trigger is running into repeated errors that are causing it to be automatically turned off.

As Jammer mentioned, can you search your emails for any notifications about errors you might have received from us? Knowing what the error message is will help us to narrow down what the issue is. If you can’t see any in your email inbox, I’d also recommend searching your spam/junk folder or searching your inbox for any emails from mail.zapier.com in case it’s been misplaced. 

That said, I’ve been looking at the Blinq pricing page and they seem to have “Card creation via API” and “Contact export via webhooks” only available to their Enterprise plan. It doesn’t expressly mention Zapier but their help guide here mentions that their Zapier integration only works with Business Contacts. So I’m wondering if that might mean that you’d need to be on their Business plan in order to use their app integration.

Can you confirm whether the paid account you have with them is on their Business plan?

Looking forward to hearing from you!

Thanks, Sam!

It shows Blinq Business:



This is the email we received:
 

 

Hi ​@nb34,

Based on the error on the screenshot, it seems like you’re encountering a 500 error. ​This type of "Internal Server Error" (500) error can happen from time to time when a server is under heavy load, or if the data trying to be passed is too large or for a whole variety of other circumstances. 

Since this happens on the other app's end we can't see exactly what might be the specific problem here, but the good news is that these issues are usually short-lived. Generally, once they settle back down.

Hopefully, this helps.

 

Terms & Conditions