See llms.txt for all machine-readable content.
New hire, new ID card, zero paperwork chaos. Called with an employee ID, this workflow looks up the employee in Google Sheets, assigns a unique employee number, renders a PDF ID card, and routes it to printing, a GA task, or digital activation. Every step logged.
Last updated: September 2026.
This workflow is called with an employee ID, looks up the employee in Google Sheets, ensures they have a unique employee number, and then creates or updates an ID card record, renders a PDF via an HTTP service, and optionally triggers printing or a GA task while logging events.
employee_id and looks up the matching employee in the Google Sheets “Employees” sheet.waiting_photo, creates a photo-request task in the “Tasks” sheet, and sends a request email via Gmail.digital_file_url, reads print_mode from the Google Sheets “Config” sheet, then either sends a print job via HTTP, creates a GA print task in Google Sheets, or marks the card as digitally activated, and finally appends an “id_card_generated” event.ONBOARDING_SHEET_URL to your onboarding spreadsheet containing the “Employees”, “ID Cards”, “Tasks”, “Events”, and “Config” sheets.ONBOARDING_HR_EMAIL to the recipient address for photo request emails.ID_CARD_RENDERER_URL (PDF renderer endpoint) and ID_CARD_VERIFY_BASE_URL (public base URL used to build verification links).PRINT_VENDOR_URL, and set the print_mode value in the “Config” sheet to PRINT_API, GA_TICKET, or DIGITAL_ONLY.What if there is no photo yet?
The card is marked waiting_photo, a task goes to the Tasks sheet, and HR gets a request email.
How is the card delivered?
Per print_mode: vendor print API, GA ticket, or digital-only activation.
What if rendering fails?
The card is marked failed with an event logged, and the workflow stops with an error.
Built with n8n. Need an assessment on your business? Feel free to reach out at https://khmuhtadin.com/consultation/