Websensepro
We are AI Automation agency specialising in N8N workflows and AI chatbots. Helping businesses automate their daily operations, reduce manual work, and boost productivity. We create custom workflow solutions tailored to each client’s unique processes, so they can focus more on growth and innovation.
Templates by Websensepro
Automate job applications with AI resume tailoring using GPT-4o, LinkedIn & Gmail
Overview Stop applying manually. This workflow acts as your personal AI recruiter, automating the end-to-end process of finding high-quality jobs, tailoring your resume, and preparing personalized outreach emails to decision-makers. What this workflow does Scrapes Real-Time Jobs: Uses Apify to pull live job listings from LinkedIn based on your specific keywords (e.g., "AI Automation"). Smart Filtering: Uses GPT-4o-mini to analyze job descriptions against your skills and automatically discards roles that aren't a good fit. Hyper-Personalized Resume: Uses GPT-4o to rewrite your "Master Resume" specifically for the target job description. Document Generation: Creates a new Google Doc with the tailored resume and automatically sets sharing permissions. Decision Maker Enrichment: Uses Anymail Finder to locate the verified email address of the Company CEO or Hiring Manager. Cold Email Draft: Generates a personalized pitch in Gmail (Drafts folder) with the link to your custom resume attached. Setup Requirements To run this workflow, you will need to set up credentials in n8n for the following services. Please ensure you use n8n credentials and do not hardcode API keys into the HTTP nodes: Google Drive & Docs: To read your master resume and create new application files. Apify Account: To run the LinkedIn Job Scraper actor. OpenAI API Key: For logic (GPT-4o-mini) and writing (GPT-4o). Anymail Finder API: To find contact email addresses. Gmail: To create the draft emails. How to use Upload Resume: Paste your "Master Resume" text into the first Google Docs node or connect your existing file. Configure Credentials: Add your API keys in the n8n credentials section for all services listed above. Set Search Criteria: Update the JSON body in the Apify node with your desired LinkedIn job search URL. Run: Execute the workflow and watch your drafts folder fill up with ready-to-send applications.
By WebsenseproAutomatically assign Jira Service Management reporter from forwarded emails
Automatically Assign Jira Service Management Reporter from Forwarded Emails This workflow solves a common problem in Jira Service Management: when an email is forwarded to create a ticket, Jira often sets the forwarding system (e.g., support@yourcompany.com) as the reporter, not the original customer. This template automates the process of parsing the original sender's details from the email body and correctly assigning them as the ticket's reporter. If the customer doesn't exist in Jira, a new customer profile is created automatically before the ticket is assigned. What it Does Triggers on New Issue: The workflow starts when a new issue is created in a specified Jira project. Filters Forwarded Emails: An If node checks if the issue was created by one of your internal forwarding email addresses. The workflow only proceeds for these specific issues. Parses Details: A Code node uses regular expressions to parse the issue description (the forwarded email's body) and extract the original sender's name and email address. Searches for Existing Customer: An HTTP Request node checks if a customer with the extracted email already exists in your Jira Service Desk. Creates New Customer: If the customer is not found, another HTTP Request node creates a new customer profile in Jira Service Management. Assigns Reporter: Finally, a Jira node updates the issue's "Reporter" field to the existing or newly created customer, ensuring the ticket is correctly associated with the original sender. Use Cases Shared Support Inboxes: Automatically process emails sent to a general support inbox (e.g., support@company.com) that are then forwarded to Jira. Departmental Forwarding: Handle tickets forwarded from specific departments (e.g., sales@company.com or billing@company.com) and assign the original sender correctly. Personal Email Forwarding: Useful when a team member forwards a customer email from their personal inbox to the Jira Service Management-connected address. Customization The Parse Details From Description node uses a regular expression (regex) to find the sender's email. The default regex is designed for standard forwarded emails that look like this: From: John Doe <john.doe@example.com> If your email client forwards emails in a different format, you may need to adjust the regex in the Code node. For example, if your format is From: [john.doe@example.com], you would need to update the regex pattern to match this structure. Troubleshooting Reporter Not Being Updated: Verify that the forwarding email addresses in the Filter Forwarding Emails node are correct. Check the body of the Jira ticket's description to ensure the forwarded email content is present and in a format the regex can parse. Customer Not Found/Created: Ensure your Jira API credentials have the necessary permissions to search for and create customers in Jira Service Management. Workflow Not Triggering: Confirm that the Jira Trigger is correctly configured for the right project and that the webhook is active in your Jira instance. Requirements An n8n instance (self-hosted or cloud). Jira Software Cloud API credentials with Service Management permissions. How to Set Up Connect Credentials: In the Jira Trigger, Jira, and HTTP Request nodes, select your Jira Software Cloud API credentials. Configure Trigger: In the Jira Trigger node, select the Jira project you want this workflow to monitor. Set Filter Emails: In the Filter Forwarding Emails (If) node, replace the placeholder email addresses with the internal email addresses that forward mail to Jira. Update Jira Domain: In both HTTP Request nodes (Search for Existing Customer and Create Customer), replace the YOURJIRADOMAIN placeholder with your actual Atlassian domain (e.g., my-company.atlassian.net). Activate Workflow: Save and activate the workflow.
By WebsenseproGenerate personalized sales follow-ups from Fireflies transcripts with Gemini & Google Drive
Automatically Generate AI Follow-Up Messages from Fireflies Transcripts This workflow automates creating personalized follow-up messages for your clients based on meeting transcripts fetched from Fireflies. It ensures the right guest information is captured, the transcript is processed by AI, and the output is stored neatly in Google Drive. What it Does Triggers on New Appointment: The workflow starts when a new appointment is created in Google Calendar. Extracts Guest and Appointment Details: The Edit Fields node extract the guest's email, appointment start/end time, status, and creator. Fetches Transcript from Fireflies: The GraphQL node queries Fireflies using the guest email to fetch the meeting transcript, including sentences, participants, and summary. Skip IF Empty: The Filter node skip passing the Info to AI Agent if there is no record in Fireflies Generates Follow-Up Messages via AI: The AI Agent node (powered by Google Gemini) creates 12 personalized follow-up messages/emails for the guest. Messages are conversational, concise, and reference topics and pain points mentioned in the call. The messages are tailored to re-engage the client and guide them towards making a purchase. Stores Messages in Google Drive: The Google Drive node saves the AI-generated messages in a specific folder, named after the guest, for easy reference. Use Cases Missed Follow-Ups: Automatically create personalized follow-ups after client calls without manual effort. Sales & Customer Engagement: Ensure every client gets context-specific messages, improving engagement and conversion. Team Collaboration: Messages are saved in Google Drive, making it easy for your team to review and send manually if needed. Customization Transcript Source: The GraphQL node can be customized to fetch transcripts for specific guests or date ranges. Message Personalization: The AI prompt in AI Agent can be updated to change the tone, style, or length of messages. Storage Folder: You can change the folder in the Google Drive node to organize messages per team, campaign, or client. Troubleshooting AI Messages Not Generated: Verify AI Agent node is connected to Google Gemini Chat Model and has correct API credentials. Messages Not Saved: Check the Google Drive folder ID and access permissions. Requirements An N8N instance (self-hosted or cloud). Google Gemini API credentials. Google Drive account with proper folder access. Fireflies API credentials with GraphQL access. How to Set Up Connect Credentials: In Google Calendar Node, GraphQL, AI Agent, and Google Drive nodes, select your credentials for Google Calendar, Fireflies, Google Gemini, and Google Drive. Set Guest Details Extraction: Verify the Edit Fields node extracts all required fields (first name, last name, email, appointment times, status). Update GraphQL Query: Ensure the query correctly fetches transcripts by guest email. Adjust if your Fireflies workspace uses different fields. Customize AI Prompt: Update AI Agent with the exact instructions for message generation (number of messages, tone, context, platform). Configure Google Drive Storage: Select the proper folder to save messages, ideally using guest name as file name for easy reference. Activate Workflow: Save and activate the workflow. Video Tutorial: Step by step video instructions present here for beginners https://youtu.be/5t9xXCz4DzM
By Websensepro