do-not-send

The do-not-send operation removes a value instead of changing it. The field is emptied, and with the right setting on the request, it is left out altogether.

Use it when an empty value is worse than no value, and when something in your data should never reach the other side.

How it works

There is no parameter. The condition does all the work.

Condition: is empty         →  the field is dropped
Condition: equals test      →  dropped only when the value is exactly "test"
Condition: always           →  the field is never sent

When the condition is not met, the field carries on as normal with its value untouched.

It works together with the request settings

do-not-send clears the value. Whether the field then disappears from the request or arrives as an empty one is decided on the HTTP request node, by the Skip field when setting.

If you want the field genuinely gone, set that to skip on null. Without it the advertiser may receive the key with nothing in it, which for some APIs is the very thing you were trying to avoid.

This is worth checking before you rely on the operation. Two integrations built the same way can behave differently here, purely because of a setting on the request rather than on the field.

When to reach for it

Empty optional fields. Some APIs are stricter about an empty value than about a missing one, and will reject a request carrying a blank field they never needed.

Test data. Keeping a placeholder from reaching a production endpoint.

Values that are only sometimes relevant. A company number that applies to the self-employed and to nobody else. Send it when it means something, drop it when it does not.

Careful with required fields

Dropping a field the advertiser requires produces a rejection, and their error message will usually name the field rather than explain that it was missing.

Before setting this up, check their documentation for what is genuinely mandatory. Where a field is required but your value is empty, set a placeholder instead of dropping it.

Finding out what was dropped

A suppressed field leaves no trace in the payload, so a request that looks wrong gives you nothing to work from.

The run log shows what the node received and returned, and {request_body} on the HTTP node shows what actually went out. Compare the two and the missing field is obvious. See HTTP request.