from-base64

The from-base64 operation decodes a Base64-encoded value back into its original string. It is the inverse of the to-base64 operation.

How it works

  • Input – a valid Base64-encoded string.
  • Output – the decoded string.
  • If the input is not valid Base64, the operation may return an empty string or the unmodified value, depending on the error handling.

Examples

Input (Base64)Output
aGVsbG8=hello
MTIzNDU=12345
eyJpZCI6MX0={“id”:1}
invalid!!“ (empty string) or unchanged

Usage in PalDock

Use from-base64 when you need to:

  • Decode API responses that provide values in Base64.
  • Convert stored tokens or payloads back into human-readable form.
  • Process binary content (files, images) that was encoded for transmission.

Best Practices

  • Always validate that the input is a valid Base64 string before decoding.
  • Be aware that decoding binary data may produce non-printable characters – only decode into text fields if the source is known to be textual.
  • Pair with to-base64 for round-trip transformations.

References

Insights that
helps you grow

  • Release notes 2026/02/27
    After months of work, our Integration Builder has a fresh new look and a lot more power. We redesigned it to be easier to use,…
  • Release notes 2025/12/19
    We added country-based categorization. You can now categorize offers, integrations, and other items by a specific country, or keep them global across all markets. We also…
  • Release notes 2025/12/17
    More flexible lead rejection: based on validation rules, filters, or pingtree sales results, by source (iframe, API) or by partner (include / exclude). It is now possible to…