Workflow Templates

Community Node Disclaimer This workflow uses KlickTipp community nodes and works only on self-hosted n8n instances. Introduction Automate Eventbrite order and refund processing by syncing data directly to KlickTipp. Whenever a participant registers or requests a refund, their profile is updated with event details and tags—keeping your segmentation accurate and automated. Who’s it for Perfect for event organizers, digital marketers, and automation specialists using Eventbrite and KlickTipp who want to eliminate manual imports and keep contact data consistent. How it works Eventbrite Trigger captures order.placed and order.refunded events. Switch Node routes logic: 🟢 Order placed → Adds contact, fetches event data, and tags buyer. 🔴 Refunded → Adds refund tag and removes buyer tag. Enrichment stores event name, page URL, and end date in KlickTipp fields. Fee check applies extra segmentation for paid vs. free events. KlickTipp updates contacts automatically—no manual steps needed. Requirements Self-hosted n8n (community node support) Eventbrite** account (OAuth2) KlickTipp** account (API access) KlickTipp custom fields: Eventbrite | Event name Eventbrite | Start timestamp Eventbrite | Event page URL KlickTipp tags: Eventbrite | Buyer Eventbrite | Refundee Eventbrite | Registrant How to set up Connect accounts: Eventbrite (OAuth2) & KlickTipp (API). Map fields: Event name, date, and URL to KlickTipp custom fields. Update tag IDs: Replace with your own KlickTipp IDs. Test the flow: Place an order → verify tags → trigger a refund to test removal. > 💡 Tip: Enable auto tag removal in KlickTipp so Buyer tags are removed when Refundee tags are added. How to customize Adapt field mappings to match your KlickTipp setup. Adjust tag rules for different event types or ticket tiers. Extend for multiple events or recurring campaigns. Campaign expansion ideas Track attendance vs. no-shows using participation tags. Add VIP or ticket-type segmentation. Trigger follow-up automations for refundees or attendees. Connect to other tools for reminders, surveys, or upsells.

What does this workflow do? This workflow acts as the backend "brain" for a sophisticated AI Voice Interviewer. It receives a user's resume text and a target job description, then uses a Large Language Model (LLM) to conduct a realistic, voice-based interview. The workflow maintains conversation history to ask relevant follow-up questions, creating a dynamic and personalized interview practice experience. This template is designed to work with a simple HTML frontend that handles the voice-to-text and text-to-speech functionality. What services does this workflow use? Google Gemini:** This is the LLM used to generate intelligent interview questions. You can easily swap this out for other models like OpenAI. What credentials do you need to have? You will need one credential: A Google Gemini API Key. You can get one for free from the Google AI Studio. How to use this workflow This workflow is the backend and requires a frontend to interact with. Set up the Frontend: You can find the complete frontend code and setup instructions in this GitHub repository. Configure Credentials: In this n8n workflow, click on the "Google Gemini Chat Model" node and add your own Gemini API credential. Activate the Workflow: Make sure the workflow is saved and active. Connect Frontend to Backend: Click on the "Webhook" node and copy the Production URL. Paste this URL into the voice-interview.html page as instructed in the GitHub repository's README.md file. Start Interviewing: Fill out the form on the web page to begin your voice interview!

Quick overview This workflow is called by another n8n workflow to export a selected n8n workflow as a JSON file and sync it to a GitHub repository, creating the file if it doesn’t exist and updating it only when the workflow definition changes. How it works Receives a workflow ID as input when executed by another n8n workflow. Fetches the workflow definition from the n8n API using the provided workflow ID. Reduces the workflow data to essential fields (such as name, nodes, connections, and settings) and converts it into a formatted JSON file. Tries to retrieve a same-named JSON file from a GitHub repository. If the file does not exist, creates it in GitHub with an initial commit message. If the file exists and the content differs from the current workflow JSON, updates the GitHub file with a new commit. Setup Create an n8n API credential with access to read workflows and select it in the n8n node used to fetch workflows. Add a GitHub credential with permission to read and write files in the target repository. Update the GitHub owner and repository values (and optionally the commit message patterns) to match where you want to store the exported workflow JSON files. Ensure the calling workflow passes a valid “Workflow Id” input when executing this workflow.

Quick Overview This workflow runs every 15 minutes to fetch approved items from a Notion content calendar, creates and schedules matching posts in Posta for the specified time, and then updates the Notion database row with the Posta post URL and a Scheduled status. How it works Runs every 15 minutes on a schedule trigger. Retrieves all pages from a specified Notion database. Processes each returned Notion row one by one, using the Caption, Scheduled At, Social Account IDs, and optional Media IDs fields. Creates a post in Posta for the selected social accounts and attaches any referenced media IDs. Schedules the Posta post for the Notion row’s Scheduled At timestamp (converted to UTC). Updates the original Notion page by setting Status to Scheduled and writing back the Posta post URL. Setup Create a Notion integration, share your content calendar database with it, and connect the Notion credentials in n8n. Add your Posta API token as Posta credentials in n8n. Set the Notion database ID/URL in the Notion database read step to point to your content calendar. Ensure your Notion database includes the required properties (Caption, Status, Scheduled At, Social Account IDs, optional Media IDs, and optional Posta Post URL) and that their names match the workflow mappings. Activate the workflow and keep the 15-minute schedule (or adjust it to match your desired posting window).

Tagged with: , , , ,

Tagged with: , , , ,

No description available

Turn new Jira tickets into automated AI coding sessions. When a ticket is created, this workflow runs an AI coding agent (Claude Code, Cursor CLI, or Codex) on the task inside a CloudCLI cloud dev environment and posts the results and the links to continue the AI coding session from mobile or an IDE, back to Jira. How it works A Jira trigger fires when a new issue is created. The ticket summary and description are composed into a prompt for the AI coding agent. CloudCLI runs the agent inside an isolated cloud container. The agent's output, VS Code and Cursor deep links, and an SSH resume command are posted back to Jira as a comment. Reviewers can open the environment in their preferred IDE or SSH in and run claude -r to resume the session from terminal. Set up steps Install the CloudCLI verified community node from the n8n nodes panel. Connect your Jira Cloud and CloudCLI API credentials. Select your target environment in the "Get Environment Details" node. Customize the prompt template in "Compose Agent Prompt" to match your codebase. Requirements Jira Cloud account CloudCLI account with API key (cloudcli.ai) A running CloudCLI environment with your repo cloned AI provider API key configured in your CloudCLI dashboard (e.g. Anthropic for Claude Code) How to customize Add an IF node to filter by label (e.g. auto-code) or issue type. Enable "Create Pull Request" in the agent's options to auto-open a PR. Add a Slack node to notify your team when the agent completes. Replace the Jira trigger with Linear, GitHub Issues, or Asana.

Turn new Linear issues into automated AI coding sessions. When an issue is created, this workflow runs an AI coding agent (Claude Code, Cursor CLI, Gemini or Codex) on the task inside a CloudCLI cloud dev environment and posts the results back to Linear with a link to the live session so you can continue your work. How it works A Linear trigger fires on issue events and filters for newly created issues only. The issue title and description are composed into a prompt for the AI coding agent. CloudCLI runs the agent inside an isolated cloud container. The agent's output, VS Code and Cursor deep links, and an SSH resume command are posted back to Linear as a comment. Reviewers can open the environment in their preferred IDE or SSH in and run claude -r to resume the session from terminal. Set up steps Install the CloudCLI verified community node from the n8n nodes panel. Connect your Linear and CloudCLI API credentials. Select your target environment in the "Get Environment Details" node. Customize the prompt template in "Compose Agent Prompt" to match your codebase. How to customize Adjust the Linear Trigger's team filter or add an IF node to filter by label (e.g. auto-code). Enable "Create Pull Request" in the agent's options to auto-open a PR. Add a Slack node to notify your team when the agent completes. Replace the Linear trigger with Jira, GitHub Issues, or Asana.

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,