Hey team, can you look at the outreach sent test column in this table? I feel like it could be a bug: https://app.clay.com/workspaces/369580/workbooks/wb_0t0qrrdnbqzmuWN2T3h/tables/t_0t0qrrhNVE4tDfvVe97/views/gv_0t0qrrhfHd4ZDBGRBmw
For Outreach integration issues, try these troubleshooting steps:
Common Outreach errors:
** "Unauthorized Request" - Records may already exist in Outreach or aren't accessible to your account
** "Relationship Resource Not Found" - Outreach needs an ID instead of email address. Edit the column, type '/id', and select the ID from the previous creation step
General column troubleshooting:
1. Delete the affected column
2. Create a fresh column
3. Re-map your data
If seeing '[object Object]' errors:
** Check if your formula references entire JSON objects instead of specific keys
** Update formula to reference specific data points (e.g., use .LinkedInOutreachMessage instead of .response)
Formula issues:
* Add conditional logic like "if {{response}} exists..." to prevent errors when data is missing
Try the Force Run option in table settings if the column isn't processing .
It breaks when I add the Deal Team column tag. everything is normal on the backend
This sounds like a formula issue where adding the Deal Team column tag is causing the column to break. The most common cause is when formulas reference data that doesn't exist for every row. Try adding conditional logic to your formula like "if {{Deal Team}} exists..." before referencing the Deal Team data. This prevents errors when the Deal Team field is empty or missing. If you're still seeing '[object Object]' errors, check if your formula is referencing the entire JSON object instead of specific keys, and update it to reference the specific data points you need. Can you copy and paste your current formula into the chat so I can help troubleshoot the specific issue?
see above
Hey — this error is coming from themselves, not Clay.
“INSERT has more expressions than target columns” means your JSON has more fields than the target (growth.outreachSent) allows.
To fix this:
** Match fields exactly to the columns in growth.outreachSent.
** If extra fields like dealteamtag or profileresearch aren’t columns, move them into a JSON column (often called customvalues). That way Supabase only sees one column instead of mismatched keys.
Example: LBKS{ "firstname": "Carina", "lastname": "Harrison", "email": "[carina.harrison@bregal.com](mailto:carina.harrison@bregal.com)", "customvalues": { "profileresearch": "…", "dealteamtag": "dealteam", "companywebsite": "[http://bregal-private-equity-partners.com/](http://bregal-private-equity-partners.com/)" } }LBKSOnce your keys align with the table schema, the POST will succeed.
Let me know if you have more questions.
It was working before
Hi, Do you still have the table where it was working before, or know which source it was pulling from? That will help us compare and see what changed. Let me know if you have more questions
It was working on this table.
I've done a bunch of comparisons and tested each column variable
It seems to be the dealteamtag specifically
and clientnametag
Hey, I ran a few tests and it all points to the same issue — the missing columns aren’t in the table. Even though they show in your view, they’re not actually part of the table itself.
Can you run these queries and send me a screenshot of the results?LBKS-- Add missing columns to the table ALTER TABLE growth."outreachSent" ADD COLUMN dealteamtag TEXT, ADD COLUMN messagetypetag TEXT, ADD COLUMN campaignname TEXT, ADD COLUMN bridgeresearch TEXT; -- Grant permissions GRANT ALL ON growth."outreachSent" TO anon, authenticated; -- Force schema cache reload NOTIFY pgrst, 'reload schema'; -- Check columns in the table SELECT column_name FROM information_schema.columns WHERE table_schema = 'growth' AND table_name = 'outreachSent' ORDER BY ordinal_position;LBKS
tbh it's gotta be a bug or something, maybe on supabase side. just sat down with my cto for 20 min troubleshooting. It works when I change the name to dealteamtag2, but not dealteamtag
