Create a table in MySQL and insert data
Companion workflow for MySQL node docs
By amudhanSlack auto translator (JA ⇄ EN) with GPT-4o-mini
🧠 How it works This workflow enables automatic translation in Slack using n8n and OpenAI. When a user types /trans followed by text, n8n detects the language and replies with the translated version via Slack. ⚙️ Features Detects the input language automatically Translates between Japanese ↔ English using GPT-4o-mini (temperature 0.2 for stability) Sends a quick “Translating...” acknowledgement to avoid Slack’s 3s timeout Posts the translated text back to Slack (public or private selectable) Supports overrides like en: こんにちは or ja: hello 💡 Perfect for Global teams communicating in Japanese and English Developers learning how to connect Slack + OpenAI + n8n 🧩 Notes Use sticky notes inside the workflow for setup details. Duplicate and modify it to support mentions, group messages, or other language pairs.
By Tomohiro GotoSend weekly hiring manager reports with BreezyHR data to email
Weekly hiring‑manager snapshot from Breezy HR to email (pipeline, next‑week interviews, stuck) This workflow sends each hiring manager a single weekly email with an overview of their open roles: pipeline totals, a per‑position summary, interviews scheduled next week and stuck candidates (no movement ≥ 7 days). It queries Breezy HR using your API token, detects the HM via each position’s team (falling back to a simple map when unavailable), aggregates results and emails one digest per HM. The job runs Mondays at 07:30 Asia/Kolkata, includes a DRY_RUN preview and rate‑limits sends. Who’s it for Hiring managers who want a once‑a‑week snapshot instead of many separate updates. Talent/recruiting teams using Breezy HR who need pipeline hygiene and next‑week readiness at a glance. Ops partners who prefer a standardized email with HTML tables and a text fallback. How it works Cron (Mon 07:30 IST) triggers weekly. Breezy → Positions: Fetch open positions (configurable). Find HM: For each position, read the position team and look for a member with a “hiring manager” role; if none, use the fallback map. Candidates per position: Fetch candidates, compute stage counts and mark stuck where last activity ≥ STUCKAFTERDAYS. Events per position: Fetch events and keep those that look like interviews scheduled next calendar week. Aggregate per position → Group by hiring manager → Build one HTML digest per HM. DRY_RUN? If true, output a preview only; otherwise send emails with a small delay between each. How to set up Credentials in n8n HTTP Header Auth for Breezy HR: set Authorization: Bearer <YOUR_TOKEN> in a credential (don’t hardcode in the node). SMTP (Gmail) to send digests. Open “Set: Config” (single place to edit) BREEZYAPIBASE = https://api.breezy.hr/v3 COMPANY_ID = your Breezy company ID TIMEZONE = Asia/Kolkata INCLUDEONLYOPEN = true (use STATE_FILTER = open) USEBREEZYHM_DETECTION = true HMFALLBACKMAP_JSON = e.g., { "Default": "hm@example.com", "Java TL": "javatl@company.com" } STUCKAFTERDAYS = 7 INTERVIEWEVENTKEYWORDS_CSV = interview SMTP_FROM = sender address SUBJECTTEMPLATE = Weekly HM snapshot {{range}} — {{positionscount}} roles, {{candidates_count}} candidates INTROTEMPLATE / OUTROTEMPLATE DRY_RUN = false (set true to preview) RATELIMITEMAIL_SECONDS = 5 Activate the workflow. Requirements Breezy HR API token with access to positions, teams, candidates and events. SMTP (Gmail) account to send emails. n8n (cloud or self‑hosted) with HTTP Header Auth and SMTP credentials. How to customize Schedule: Change Cron to your preferred day/time. Scope: Set INCLUDEONLYOPEN=false to include other position states. Interview detection: Edit INTERVIEWEVENTKEYWORDS_CSV to match your account’s event labels. Stuck threshold: Adjust STUCKAFTERDAYS (e.g., 10 or 14). Templates: Update SUBJECTTEMPLATE, INTROTEMPLATE, OUTRO_TEMPLATE. Fallback mapping: Expand HMFALLBACKMAP_JSON for positions lacking team data. Add‑ons Slack delivery: Post a weekly summary to a channel or DM the HM alongside the email. CSV attachments: Attach per‑HM CSV of positions/candidates for offline work. Manager CC: CC a recruiting lead or HRBP for visibility on key roles. Writeback: Log weekly metrics to Google Sheets for dashboards. Custom windows: Use a different future window (e.g., interviews in the next 2 weeks). Use Case Examples Busy HMs who want one email showing where to focus for the coming week. Recruiting Ops keeping tabs on pipeline health and stalled candidates. Leadership reviews where weekly snapshots feed into Monday stand‑ups. Common troubleshooting | Issue | Possible Cause | Solution | |---|---|---| | No emails sent | DRYRUN=true | Set DRYRUN=false to send. | | Missing HM recipients | Team endpoint returned no “hiring manager” and fallback map not configured | Add position→email in HMFALLBACKMAP_JSON (or set a better default). | | Interviews list is empty | Different event label in your Breezy account | Add your labels to INTERVIEWEVENTKEYWORDS_CSV (comma‑separated). | | Stuck candidates not flagged | Threshold too high or activity timestamps missing | Lower STUCKAFTERDAYS or verify candidate activity data. | | API errors | Bad token or insufficient scopes | Recreate the Breezy credential with a valid Bearer token. | | Emails fail to send | SMTP auth/quota issues | Check SMTP credentials/from‑address permissions and provider limits. | Need Help? If you’d like help tuning the interview filters, changing the grouping logic, or adding Slack/CSV writebacks, feel free to reach out our n8n experts at WeblineIndia. We'll be happy to help you tailor this to your stack.
By WeblineIndia