Error: Expected array, received string in Clay Campaign Launch

Mehdi A. · 2025-10-21T23:10:35.105Z

Hey! I've launched my first campaign in Clay and get the following error attached. {"issues":[{"code":"invalid_type","expected":"array","received":"string","path":["request","campaign_ids"],"message":"Expected array, received string"}],"name":"ZodError"} I tested emails before launching and it worked well. Link to the campaign. (https://app.clay.com/workspaces/493425/workbooks/wb_0t48d06Cwsmxo2dNkDp/tables/t_0t48ebrxRWECraMswMg/views/gv_0t48ebuviXneowGvVX3) Please advise on how to solve.

Error: Expected array, received string in Clay Campaign Launch | Clay

Clay Support
APP
·
·
This error indicates that the campaign_ids field is receiving a string value when it expects an array format.
The issue is likely in your JSON formatting where campaign_ids should be formatted as an array with square brackets, like ["campaign_id_1", "campaign_id_2"] instead of just a string value.
To help troubleshoot this further, could you copy and paste the JSON configuration you're using for your campaign setup? This will allow me to identify the specific formatting issue and provide the correct syntax. [1]
Mehdi A.
·
·
Where can I find the JSON configuration I'm using for my campaign setup?
Clay Support
APP
·
·
The JSON configuration is in the Body section of your HTTP API integration within your campaign setup. [1]
To find it:
1.
Navigate to your campaign in Clay
2.
Look for the HTTP API enrichment you're using
3.
Open the configuration and check the Body section [2]
The Body contains your JSON data that's being sent with the API request. Please copy and paste that JSON from the Body section so I can identify the specific formatting issue with your campaign_ids field. [3]
Clay Support
APP
·
·
Did that answer your question?
Mehdi A.
·
·
No It didn't I don't see any HTTP API enrichment I'm using in my campaign.
Clay Support
APP
·
·
Thanks for letting me know. I’m routing you to our human team now so they can assist you further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Loading attachments
Mehdi A.
·
·
https://app.clay.com/workspaces/493425/workbooks/wb_0t48d06Cwsmxo2dNkDp/tables/t_0t48d0lEZgcdboSE8nr/views/gv_0t48d0lDgwQY588oeBX
Aditi S.
·
·
Hi Mehdi - thanks so much for reaching out and for your patience here. Are you still facing this issue? I am not seeing the error you mention pop up when checking your campaign.
Mehdi A.
·
·
Hey Aditi S. - The issue is gone but the emails are being delivered very slowly.
Aditi S.
·
·
Understood - for the slower pacing is actually intentional! Clay Sequencer spaces out sends (about 1 every ~20 minutes, 9am–5pm, up to 30/day per inbox) to protect your deliverability.
This pacing mimics human sending, which helps your emails land in inboxes instead of spam. If you’d like to send faster, you can connect more inboxes or adjust the schedule settings, though we recommend keeping the defaults for best results.
Mehdi A.
·
·
Aditi S. Got it! Is there a way to increase the max 30 sends per inbox?
Luca P.
·
·
The 30 sends per inbox per day is a deliverability safeguard we've set to protect your sender reputation and ensure emails land in inboxes, not spam. While we're working on allowing users to adjust this limit, we generally don't recommend increasing it as going higher can negatively impact deliverability.
The best way to scale your sending is to connect additional inboxes to your campaign. For example, if you need to send 300 emails per day, connecting 10 inboxes would get you there while maintaining healthy sending patterns. This approach keeps your domains in good standing with email providers!"
Mehdi A.
·
·
Thanks Luca P.
Sayli G.
·
·
Hello Mehdi! Thanks for reaching out! Jumping in for Aditi and Luca. I can see they answered all your questions. Is there anything else that we can help you with?

16 comments