Zoom → TempWorks Recruiting Integration

An event-driven recruiting workflow connecting Zoom, Microsoft Azure services, and TempWorks to move call transcripts into the correct recruiter record.

Zoom → TempWorks Recruiting Integration preview
Role
Integration Developer / Automation Engineer
Status
Implemented

Project overview

SkillsetGroup recruiters needed Zoom call transcripts associated with the correct TempWorks contact and available inside the staffing system as notes. The existing manual workflow required transcript retrieval, contact lookup, matching, and note entry.

I designed and implemented an event-driven integration that connected those steps while keeping TempWorks as the system recruiters already used. The engagement began as direct freelance work; portions of later work or payment transitioned under Nexx Systems LLC.

The implemented workflow

  1. A Zoom call event sends a webhook.
  2. The webhook invokes an Azure Function written in TypeScript and running on Node.js.
  3. The function retrieves the call transcript.
  4. Azure Data Factory orchestrates the downstream TempWorks data workflow.
  5. TempWorks contact data is retrieved and stored in Azure Cosmos DB.
  6. The workflow correlates transcript and caller information with the appropriate TempWorks contact.
  7. The transcript is posted to TempWorks as a recruiter note.
Public-safe architecture of the implemented Zoom-to-TempWorks workflow.
Public-safe architecture of the implemented Zoom-to-TempWorks workflow.

Engineering concerns

The useful part of this project was not simply calling several APIs. The workflow had to cross systems with different identifiers and responsibilities, so validation, data matching, recoverability, retries, reconciliation, structured logging, and technical documentation were part of the design.

Outcome

The integration replaced a multi-step manual path with one connected workflow and made call information available inside the staffing system where recruiters already worked.

No percentage-based time-savings or performance claim is included because I do not have a measurement source that I can defend publicly.

Public-use note

The diagram is intentionally simplified. It uses synthetic labels and does not expose transcripts, candidate or contact records, credentials, tokens, private identifiers, or confidential endpoints. Azure Data Factory was used for orchestration; Microsoft Power Automate was not used for this project.

Technologies used

Azure Data FactoryAzure FunctionsTypeScriptNode.jsAzure Cosmos DBZoom WebhooksTempWorks APIREST APIsJSON