[New Mission] Operative NextGen: Automate hiring with workflows

Summary

Author the event-driven hiring automation mission. Learners build a Workflow that starts when a resume arrives by email, validates and files the attachment, invokes the hiring capability to create records, and posts an Adaptive Card to a recruiting team in Microsoft Teams.

This replaces the classic agent-level Power Automate trigger with a first-class Workflow in the modern Copilot Studio experience. Duplicate checks found no issue proposing this complete Operative NextGen mission.

Proposed mission

Scenario

Candidates submit resumes through a monitored inbox. The workflow must recognize eligible messages, preserve the source file, create the correct hiring records through the agent or supported Dataverse operations, and alert recruiters with a concise Teams card and link to the application.

Use a mailroom analogy: the workflow receives and validates each package, routes it through intake, files the records, and alerts the responsible team.

Mission objectives

• Explain autonomous Workflows and connector triggers.
• Process supported resume email attachments safely.
• Invoke the Hiring Agent or supported hiring capability from a Workflow.
• Create and verify hiring records.
• Post a Teams Adaptive Card with traceable application details.
• Monitor runs and handle failures.

Prerequisites to state in the mission

• Completion of Missions 01–06.
• A dedicated test mailbox and Teams test channel.
• Outlook, Dataverse, and Teams connection permissions.
• Supplied fictitious resume files.
• Permission to create and publish Workflows.

Proposed lab outline

Create the email-triggered Workflow

Use the current Outlook email-arrival connector trigger. Scope the monitored folder or subject, include attachments, and reject missing, multiple, oversized, or unsupported files according to the documented policy.

File and process the resume

Preserve filename, content, sender, timestamp, and message identifier. Invoke the Hiring Agent through the supported Agent node or call a bounded intake operation. Prevent duplicate processing through a stable idempotency key.

Create records and notify Teams

Confirm Candidate, Resume, and Job Application records exist, then post an Adaptive Card containing only necessary data, status, and a valid Hiring Hub link. Avoid exposing resume contents in Teams.

Test and monitor

Test a valid resume, duplicate email, no attachment, unsupported type, multiple attachments, and downstream failure. Inspect run history, retries, error paths, records, and card output.

Acceptance criteria

• Build the automation in the modern Workflows experience, not a classic agent trigger.
• Validate current trigger, Agent node, connector action, and publishing labels live.
• Document mailbox and Teams prerequisites before the lab.
• Apply file type, count, and size checks before processing.
• Implement idempotency so retries or duplicate messages do not create duplicate applications.
• Preserve source traceability without posting sensitive resume data to Teams.
• Create valid Candidate, Resume, and Job Application records or verify the agent-created records.
• Post a channel-compatible Adaptive Card with an accessible Hiring Hub link.
• Include explicit failure handling and a safe test cleanup path.
• Inspect run history and verify each end-to-end side effect.
• Preserve <mission-meta /> and the Operative Mission 07 analytics tag.
• Follow repository writing and validation standards.

Out of scope

• Production shared-mailbox provisioning.
• Complex approval chains.
• Third-party applicant tracking systems.
• Scheduled reporting and bulk historical imports.

Risks

• Email triggers can be delayed and can reprocess messages after retries.
• Large or malicious attachments require policy controls beyond a tutorial.
• Agent invocation from Workflows can vary by tenant rollout.
• Teams card schema support differs by channel and client.
• Maker-owned connections can create production ownership risk.

References

• Current trigger mission
• Operative v2 workflow preview
• Office 365 Outlook connector
• Microsoft Teams connector
• Adaptive Cards