If someone recommends “Request Token Encoding: None” in a webhook, always push back
A client recently asked about connecting Marketo to Clay and we were dismayed at Clay’s official docs:
Snippet from Clay docs
See how they recommend Request Token Encoding: None? That’s totally wrong, since:
There are {{lead.tokens}} in the body, i.e. request tokens.
The body uses URL encoding, indicated by the & and = delimiters.
You must URL-encode tokens in a URL-encoded body.
This webhook setup instantly breaks with a Company like Jack & Jill Construction. It’s kind of inconceivable that they tested it at all.
Moreover, when you actually set up a webhook receiver in the Clay app, it says the payload is supposed to be JSON-encoded, not URL-encoded! So their doc feels like a hallucination. You should actually be using a payload like this:
{
"first_name" : {{lead.First Name}},
"last_name" : {{lead.Last Name}}
}
And of course set Request Token Encoding: JSON.
Why would you ever use Request Token Encoding: None?
In 2 rare cases, None is cor
