Cross-Feature Interactions

​

Overview

Firstwork’s modules are deeply interconnected. This document maps every cross-module relationship — how data flows between features, which modules can trigger actions in others, and what shared infrastructure connects them.

---

​

Module Interaction Map

---

​

Hiring Flows and Automations

This is the most common integration in the platform. Automations respond to hiring flow events:

• Stage and status changes trigger “On Change” automations
• Form element submissions trigger “Form Element Submission” automations
• Recollection events trigger “Recollection” automations
• External API application creation triggers “External API” automations

Automations act on hiring flow data:

• Update application stage or status
• Fill form fields with data
• Create contracts from applications
• Reset custom links for re-entry
• Trigger recollection requests
• Run OCR on uploaded documents

---

​

Hiring Flows and AI Caller

How they connect:

• An AI Caller bot can be embedded as a form element within a hiring flow page
• When the candidate reaches that step, a call (phone, audio, or video) is initiated
• Input data is pulled from the candidate’s application
• Output data is written back to form fields through configured mappings
• The form can be configured to block progression until the call completes

---

​

Hiring Flows and Scheduler

How they connect:

• A scheduling element within a form page links to a specific event
• The candidate is presented with a calendar and available time slots
• Booking data (date, time, status) is stored as part of the application
• Rescheduling and cancellation are available from within the application context

---

​

Hiring Flows and AI Agents

How they connect:

• An AI Agent element within a form page triggers browser automation when the candidate reaches that step
• The agent’s input variables are populated from the application data
• Output variables are mapped back to form fields

---

​

Hiring Flows and LMS

How they connect:

• Compliance rules can include “Assign Courses” as an action, automatically enrolling candidates in training based on their data
• Automations triggered by hiring flow events can also enroll candidates in courses
• Course completion status is available as data for further compliance evaluation

---

​

Hiring Flows and People/Onboarding

How they connect:

• The “Create Contract” automation action converts a completed application into a worker contract
• The contract is assigned an onboarding flow
• The candidate transitions from the Applicant role to the Worker role
• Application data carries over to the contract and onboarding context

---

​

Automations and AI Caller

• The “AI Caller” automation action triggers a call enrollment
• Call results (transcript, captured answers, status) become available for subsequent automation actions

---

​

Automations and Scheduler

• The “Event Action” automation action creates or manages scheduler events
• Automations can be configured to respond to booking-related events (via On Change triggers)

---

​

Automations and LMS

• The “Assign Courses” automation action enrolls candidates or workers in courses
• Course enrollment and completion events can trigger downstream automations

---

​

Automations and AI Agents

• The “Run AI Agent” automation action triggers agent execution
• Agent output data feeds into subsequent automation actions

---

​

Automations and External Integrations

Automations connect to external services through:

---

​

Automations and Check-in Forms

• “Send Check-in Form” action sends a form to a worker
• “Update Check-in Form Status” action changes a submission’s status
• Automations can be scoped to check-in forms, responding to submission events

---

​

Automations and People/Onboarding

• “Create Contract” action creates a worker contract
• “Update Worker Stage” action modifies the contract status
• Automations scoped to People/Onboarding respond to contract events

---

​

Shared Infrastructure

​

Form Builder

The Form Builder is the universal form engine used by:

​

Compliance Engine

The compliance rule engine is used for decision-making in:

• Form pages — Navigation, recollection, and assignment rules
• Automations — Rule evaluation actions and schedule filter rules
• Custom Variables — Rule-based variable computation
• Data Connectors — Conditional data mapping

​

Dynamic Data (Object Graph)

All modules share access to a unified data layer that provides dynamic references to:

• Candidate and user profile data
• Application and form submission data
• Company and legal entity configuration
• Automation variables and custom variables
• Course enrollment data
• Check-in form data

This shared data layer enables dynamic templates, conditional logic, and cross-module data references.

---

​

Background Processes