Wyeth
Templates by Wyeth
Convert JSON objects to base64 strings with file processing
Encode JSON to Base64 String in n8n This example workflow demonstrates how to convert a JSON object into a base64-encoded string using n8n’s built-in file processing capabilities. This is a common requirement when working with APIs, webhooks, or SaaS integrations that expect payloads to be base64-encoded. > Tip: The three green-highlighted nodes (Stringify → Convert to File → Extract from File) can be wrapped in a Subworkflow to create a reusable Base64 encoder in your own projects. --- 🔧 Requirements Any running n8n instance (local or cloud) No credentials or external services required --- What This Workflow Does Generates example JSON data Converts the JSON to a string Saves the string as a binary file Extracts the file’s contents as a base64 string Outputs the base64 string on the final node --- Step-by-Step Setup Manual Trigger Start the workflow using the Manual Execution node. This is useful for testing and development. Create JSON Data The Create Json Data node uses raw mode to construct a sample object with all major JSON types: strings, numbers, booleans, nulls, arrays, nested objects, etc. Convert to String The Convert to String node uses the expression ={{ JSON.stringify($json) }} to flatten the object into a single string field named json_text. Convert to File The Convert to File node takes the jsontext value and saves it to a UTF-8 encoded binary file in the property encodedtext. Extract from File This node takes the binary file and extracts its contents as a base64-encoded string. The result is saved in the base64_text field. --- Customization Tips Replace the sample JSON in the Create Json Data node with your own payload structure. To make this reusable, extract the three core nodes into a Subworkflow or wrap them in a custom Function. Use the base64_text output field to post to APIs, store in databases, or include in webhook responses.
Create debug breakpoints and logs with Slack interactive messages
How it Works: You can now use the Slack node to create conditional breakpoints! This example shows the loop stop on 4 (of 10) and then you can hit "continue" in Slack when you are ready. You could extend this with a Form node and inject values you type in on the fly. Slack was already the best place to debug log n8n, and now it just got better!
INST - the n8n installer: deploy workflows with automatic credential mapping
INST: The n8n Workflow Installer This workflow provides everything you need to package and deploy multiple workflows from a single workflow you distribute. That's right, now you can package up dozens of workflows and send your client(s) a single workflow to run, that will create them all and auto-assign all the credentials. This workflow installs 3 files when you run it, demonstrating the functionality. Just make your own mods to the system, repackage it, and you are ready to go! --- Requirements An n8n instance with API access enabled and an access key Optional: GitHub and OpenAI access keys --- What This Workflow Does Installs 3 additional workflows, demonstrating the functionality One of the workflows is a packager, that you configure for your own needs Two example workflows demonstrate functionality, and can be deleted --- Step-by-Step Setup Run the Workflow This will get the example and tool workflows on your instance. Package Your Content Configure the packager, then run it to produce a base64-compressed version of your files. Customize the Installer Make your own copy of the installer, and set the base64 payload. Deploy the Installer Export your installer script. Now, anyone you send it to will get all your packaged workflows when they execute it. --- How to Use This Workflow This workflow is meant to be reused and adapted. You can: Integrate it into a deployment pipeline Turn it into a subworkflow for dynamic installs Extend it to include triggers, permission settings, or test runs If you frequently deploy or share n8n assets, this installer gives you a repeatable way to do it with confidence.