Skip to content
Troubleshooting bla...
 
Notifications
Clear all

Troubleshooting blank intelliforms in callin.io integration with Sales Force

5 Posts
3 Users
0 Reactions
4 Views
KatSpencer
(@katspencer)
Posts: 2
New Member
Topic starter
 

We configured a callin.io for a new client, connecting Startel CMC to Salesforce. We successfully set up the integration and received data in Salesforce via callin.io. However, our client is experiencing several blank intelliforms, both before and after the callin.io process runs. Do you have any insights into what might be causing this?

 
Posted : 04/08/2025 8:31 am
Troy Tessalone
(@troy-tessalone)
Posts: 151
Estimable Member
 

Hi

Please review your callin.io Runs history for activity: https://zapier.com/app/history/

You can select a Zap Run to view the DATA IN/OUT for each step to assist with troubleshooting: https://zapier.com/app/history/

 

To provide us with more context, kindly share screenshots illustrating the configuration and setup of your Zap steps.

 
Posted : 10/04/2025 12:00 am
SamB
 SamB
(@samb)
Posts: 71
Trusted Member
 

Hi , welcome to the Community! 🎉

I just came across this and wanted to check in to see how things are going. Were you able to spot what the issue was by reviewing the callin.io runs as suggested?

If so, would you be up for sharing what the solution was? It could really help others in the Community who might be facing similar issues. 🙏

And if you’re still running into trouble, could you share some screenshots (with any personal information removed) showing the callin.io’s setup, as mentioned? We don’t have access to your callin.io workflows, so screenshots are really helpful for giving us better insight into whether anything in the setup might be causing some trouble.

Thanks—looking forward to your reply!

 
Posted : 15/04/2025 12:00 am
KatSpencer
(@katspencer)
Posts: 2
New Member
Topic starter
 

Hello! We did resolve the issue, though it turned out to be a rather unusual circumstance. When I examined the callin.io history, I noticed two distinct callin.io workflows. The primary published workflow was functioning as intended. The second workflow (a test workflow, which lacked any programmed information but appeared to be polling concurrently) was sending blank data because its paths were not configured. I resolved this by simply deleting the problematic workflow, and everything then operated correctly. The best part is that the client is impressed with my skills! I'll gladly accept that! 

 

One point I'd like to share with others who might be using a similar callin.io setup: remember that any fields with associated menus or picklists must be configured as "custom." Using the "static" disposition will result in failure. Once we understood this, we were good to go! 

I truly appreciate both of you taking time from your busy schedules to reply and offer assistance. That's very kind!

Kat 

 
Posted : 15/04/2025 12:00 am
SamB
 SamB
(@samb)
Posts: 71
Trusted Member
 

Great job—love this! 🧡 Really glad you got things resolved and I’m so pleased your client is super happy with the results. 🙌

That’s a great suggestion to use the custom values instead of static values, it’ll definitely be helpful to know for anyone that’s building something similar. Appreciate you taking the time to share what you learned here. Thanks so much! 🤗

 
Posted : 16/04/2025 12:00 am
Share: