Email waterfall API key issue with Datagma account needs fixing in email automation process

Hi. I'm having an issue with the email waterfall. When I first run it, the API key for Datagma appears as if there isn't any, which is okay, but when it needs to find the email it appears as if the API key for my Datagma account is on. Could anybody fix this? I don't want to do it manually for each table that I run email waterfall for

✅1

6 comments

Pilar V.
·
·
This is one example. It happens to all my tables https://app.clay.com/workspaces/45767/tables/t_VcCwXQlwK153/views/gv_Yq58A2e3pn3z
Clay T.
APP
·
·
Hey Pilar, thanks for reaching out, sorry for the delay!
Clay T.
APP
·
·
To clarify, do you want to use your Datagma key or Clay's?
Pilar V.
·
·
Clays!
Pilar V.
·
·
As my datagma credits renovated this day, it now runs in my new tables; but still, I didn't put that it should run with those credits
Clay T.
APP
·
·
Got it! Yeah, our default, and because many users requested this was to automatically select their key when adding an integration if they had connected one into Clay.Let me know if you run into this issue again when you explicitly Clay's account instead but doesn't save the settings. Would be happy to bring that up to quickly fix the issue.