Skip to content
Troubleshooting cus...
 
Notifications
Clear all

Troubleshooting custom metadata variables in callin.io for callin.io integration

3 Posts
3 Users
0 Reactions
5 Views
Xavier from Lexa
(@xavier-from-lexa)
Posts: 1
New Member
Topic starter
 

Hello everyone,

I'm attempting to initiate a phone call using callin.io through Zapier and pass custom metadata variables into my callin.io Pathway (such as lead name, company, budget, etc.).

Here's precisely what I'm doing:

- Within the "Send Phone Call in callin.io" Zapier action, I'm populating the **Metadata field (the lower one)** with this raw JSON:

{
  "leadFullName": "XXX",
  "company": "XXX",
  "typeOfService": "XXX",
  "industry": "XXX",
  "geography": "XXX",
  "searchDescription": "XXX",
  "budgetRange": "XXX",
  "listOfQuestionsAndPointsToClarify": "XXX"
}

- The field above Metadata is left entirely blank.
- I am **not** utilizing "Extract Call Info into Variables" within the callin.io Pathway.
- In my callin.io prompt, I reference the variables like `[leadFullName]`, `[company]`, `[searchDescription]`, and so on.

However, during test calls, callin.io does not resolve the variables; the bot literally says "Hi [leadFullName]" instead of inserting the actual value.

Is there a known issue with metadata transmission via Zapier to callin.io?  
Do I need to format the field differently or configure something else in the Zap?

Thank you very much in advance for your assistance!
 

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

Hi

For us to have true context, please post screenshots showing how your callin.io step is configured in EDIT mode with the field mappings visible in the CONFIGURE tab.

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

Hey ​👋

Not sure if you’ve already got this sorted but I noticed the Metadata field’s help text includes this example, which is a bit different to what you’re using:

 

{ "metadata": { "campaign_id": { "campaign_id": "1234" }, "source": { "source": "web" } } }

It looks like your custom fields need to be nested under metadata. Try this JSON instead (replace XXX with the relevant mapped fields):

{ "metadata": { 
    "leadFullName": "XXX",
    "company": "XXX",
    "typeOfService": "XXX",
    "industry": "XXX",
    "geography": "XXX",
    "searchDescription": "XXX",
    "budgetRange": "XXX",
    "listOfQuestionsAndPointsToClarify": "XXX"
  }
}

Let us know how it goes! 🙂

 
Posted : 24/07/2025 12:00 am
Share: