Bo (.

Good news! Happy to report that we heard back from the team and this issue should be fixed.

Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble.

Thank you for your patience as we worked on it.

Yes.

In Clay, the forward slash /Column Name is how you reference a column value. It’s not a token.

That also means {{ }} or #{{ }} shouldn’t be used. Those won’t resolve and get sent literally.

Use /Column Name inside quotes instead.

Let me know if you have more questions.

Glad to hear. Earlier, there were no values being linked with the forward slash still ! :)

Hey,

The hardcoded test proves Attio is fine with the format. What’s breaking here is the templating, not the domain itself.

In the logs, Clay is sending the placeholders literally (ex: {{Clean Domain for Attio}}) instead of substituting the row value. That’s why Attio returns “Invalid Domain”.

So the fix is: don’t use #{{ }} in the HTTP API body. Use Clay column references instead.

Use this in the body:

Once those are /... references, Clay will populate them per row and the request should stop failing.

Let me know if you have more questions.

Willy - Do you mind sending the link (url) to the table so we can take a look?

Would you mind recording a quick video so I can share it with the team, just in case?

Same!!! :) Cheers !

Technology 😅 haha Happy Saturday!

Also: it looks enabled on our side now. Can you try using @Clay again and share what happens (or a screenshot if it still fails)?

Can you record yourself connecting to Clay after clicking Continue to Clay?