by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by Sarry
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!
by KlickTipp
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.
by KlickTipp
Community Node Disclaimer: This workflow uses KlickTipp community nodes. Introduction This workflow creates a complete two-way synchronization between KlickTipp and Google Calendar. When a contact in KlickTipp is tagged, an event is automatically created in Google Calendar. If event status changes or if attendees respond, their RSVP status and event status are reflected in KlickTipp — keeping your contact database, campaigns, and event insights always up to date. Perfect for marketers, coaches, or event organizers who want to automatically send event invites and instantly capture participation status without manual updates. How it works Google Calendar → KlickTipp: This template keeps your KlickTipp list in sync with Google Calendar across the full event lifecycle. For each attendee, the workflow optionally filters out internal domains, then writes event details into KlickTipp custom fields. It watches your calendar for: Event Created* → creates/updates each attendee as a KlickTipp contact and adds the *event created/updated tag. Event Cancelled* → tags attendees with *event canceled. Event Updated* → routes attendees by *responseStatus** and tags them: accepted → event confirmed declined → event declined tentative → event considered KlickTipp → Google Calendar: Watches for a tag like “Send an event invitation via Google Calendar”. Creates an event in Google Calendar using mapped KlickTipp fields. Setup Instructions KlickTipp Preparation Prepare custom fields Google Calendar | event summary, data type: "Single line" Google Calendar | event description, data type: "Single line" Google Calendar | event location, data type: "Single line" Google Calendar | event start datetime, data type: "Datetime" Google Calendar | event end datetime, data type: "Datetime" Prepare tags: Google Calendar | event created/updated Google Calendar | event canceled Google Calendar | event declined Google Calendar | event confirmed Google Calendar | event considered Send an event invitation via Google Calendar Prepare outbound: Activation tag: Send an event invitation via Google Calendar Activation URL: webhook URL from trigger Credential Configuration Connect your Google Calendar account using Client ID and Client Secret from the Google Cloud. Authenticate your KlickTipp connection with username/password credentials (API access required). Customization Recommended poll frequency: every 1–5 minutes for near real-time updates. Adjust to your local timezone if necessary. Each trigger works independently, allowing partial deployments if only certain event types are needed. Ensure End > Start in your data. If you prefer a fixed duration, compute End from Start + minutes in a Date & Time node. If you want a Meet link, enable “Add Google Meet video conferencing” in the Calendar node instead of pasting a Calendar URL into Location.
by System Admin
Tagged with: , , , ,
by System Admin
No description available