Elodie Tasia
Workflows by Elodie Tasia
Create Branded Social Media Images with Bannerbear (Sync/Async modes)
Automatically create branded social media graphics, certificates, thumbnails, or marketing visuals using Bannerbear's template-based image generation API. **Bannerbear's API is primarily asynchronous by default**: this workflow shows you how to use both asynchronous (webhook-based) and synchronous modes depending on your needs. ## What it does This workflow connects to Bannerbear's API to generate custom images based on your pre-designed templates. You can modify text, colors, and other elements programmatically. By default, Bannerbear works asynchronously: you submit a request, receive an immediate 202 Accepted response, and get the final image via webhook or polling. This workflow demonstrates both the standard asynchronous approach and an alternative synchronous method where you wait for the image to be generated before proceeding. ## How it works 1. **Set parameters** - Configure your Bannerbear API key, template ID, and content (title, subtitle) 2. **Choose mode** - Select synchronous (wait for immediate response) or asynchronous (standard webhook delivery) 3. **Generate image** - The workflow calls Bannerbear's API with your modifications 4. **Receive result** - Get the image URL, dimensions, and metadata in PNG or JPG format **Async mode (recommended):** The workflow receives a pending status immediately, then a webhook delivers the completed image when ready. **Sync mode:** The workflow waits for the image generation to complete before proceeding. ## Setup requirements - A Bannerbear account (free tier available) - A Bannerbear template created in your dashboard - Your API key and template ID from Bannerbear - For async mode: ability to receive webhooks (production n8n instance) ## How to set up 1. **Get Bannerbear credentials:** - Sign up at bannerbear.com - Create a project and design a template - Copy your API key from Settings > API Key - Copy your template ID from the API Console 2. **Configure the workflow:** - Open the "SetParameters" node - Replace the API key and template ID with yours - Customize the title and subtitle text - Set `call_mode` to "sync" or "async" 3. **For async mode (recommended):** - Activate the "Webhook_OnImageCreated" node - Copy the production webhook URL - Add it to Bannerbear via Settings > Webhooks > Create a Webhook - Set event type to "image_created" ## Customize the workflow - Modify the template parameters to match your Bannerbear template fields - Add additional modification objects for more dynamic elements (colors, backgrounds, images) - Connect to databases, CRMs, or other tools to pull content automatically - Chain multiple image generations for batch processing - Store generated images in Google Drive, S3, or your preferred storage - Use async mode for high-volume generation without blocking your workflow
Create structured logging system with Supabase and Log4j2-style levels
Create centralized, structured logs directly from your n8n workflows, using Supabase as your scalable log database. Whether you're debugging a workflow, monitoring execution status, or tracking error events, this template makes it easy to log messages in a consistent, structured format inspired by Log4j2 levels (DEBUG, INFO, WARN, ERROR, FATAL). You’ll get a reusable sub-workflow that lets you log any message with optional metadata, tied to a workflow execution and a specific node. ## What this template does - Provides a sub-workflow that inserts log entries into Supabase. - Each log entry supports the following fields: - workflow_name: Your n8n workflow identifier - node_name: last executed node - execution_id: n8n execution ID for correlation - log_level: One of DEBUG, INFO, WARN, ERROR, FATAL - message: Textual message for the log - metadata: Optional JSON metadata (flexible format) - Comes with examples for diffrerent log levels: Easily call the sub-workflow from any step with a Execute Workflow node and pass dynamic parameters. ## Use Cases - Debug complex workflows without relying on internal n8n logs. - Catch and trace errors with contextual metadata. - Integrate logs into external dashboards or monitoring tools via Supabase SQL or APIs. - Analyze logs by level, time, or workflow. ## Requirements To use this template, you'll need: - A Supabase project with: - A log_level_type enum - A logs table matching the expected structure - A service role key or supabase credentials available in n8n. The table shema and SQL scripts are given in the template file. ## How to Use This Template - Clone the sub-workflow into your n8n instance. - Set up Supabase credentials (in the Supabase node). - Call the sub-workflow using the Execute Workflow node. - Provide input values like: ``` { "workflow_name": "sync_crm_to_airtable", "execution_id": {{$execution.id}}, "node_name": "Airtable Insert", "log_level": "INFO", "message": "New contact pushed to Airtable successfully", "metadata": { "recordId": "rec123", "fields": ["email", "firstName"] } } ``` - Repeat anywhere you need to log custom events.