Keep the handoff clear. Know what connects today.

Review payroll records in Attlock and export them for your provider's upload process. Direct payroll provider connections are planned; they are not available today.

Planned and export-only provider workflows

Planned or export-only workflows. A provider logo is not a live connection or a partnership.

Planned and export-only provider workflows. Authored example; changes stay in this preview.

Review here. Process with your provider.

  1. 1

    Review the records

    Confirm hours, pay rules, and exceptions with the responsible team before preparing the export.

  2. 2

    Export and check

    Prepare the payroll records and check their fields against the format your provider accepts. An export is a file handoff, not a direct connection.

  3. 3

    Complete the provider workflow

    Upload and review through your payroll provider. Payment processing, tax filing, and provider confirmation happen through that workflow.

01

Payroll exports

Review and export payroll records for upload through your provider. Confirm the provider's required columns and process before relying on a particular file format.

Attlock Integrations & Exports

Payroll exports

Review and export payroll records for upload through your provider. Confirm the provider's required columns and process before relying on a particular file format.

Review the source record before taking the next step.
02

Direct provider connections · Planned

Direct payroll provider connections are not available yet. A provider name or planned connection does not mean that records synchronize automatically.

Attlock Integrations & Exports

Direct provider connections · Planned

Direct payroll provider connections are not available yet. A provider name or planned connection does not mean that records synchronize automatically.

Review the source record before taking the next step.
03

An honest integration conversation

Bring your provider and data requirements to the team. Confirm the supported workflow, availability, and responsibilities before changing your process.

Attlock Integrations & Exports

An honest integration conversation

Bring your provider and data requirements to the team. Confirm the supported workflow, availability, and responsibilities before changing your process.

Review the source record before taking the next step.

Attlock does not claim to transmit wages, file payroll taxes, or synchronize with a payroll provider through the export workflow shown here.

The Attlock family. Separate products, one team.

Growth and Attforce are their own products with their own workspaces. Company records are not shared between them and Attlock Operations without a permissioned, recorded connection.

  • Attlock LogoAttlock GrowthSeparate

    Contract research and reviewed outreach

    Research contract opportunities, check fit against your service area and capacity, and prepare outreach that a person approves. A separate product from Attlock Operations, for owners and growth teams.

    Explore Attlock Growth
  • Attforce by AttlockComing soon

    Scheduling and hours for hourly teams

    Scheduling, clock-ins, shift tasks, and reviewed hours for hourly teams in cleaning, facilities, retail, events, warehouses, and construction. A separate product for the people keeping work moving.

    Explore Attforce
  • Attlock LogoAttlock AIComing soon

    Operational intelligence

    Operational dashboards and exports are separate from the planned Attlock AI intelligence layer. Reviewing a chart does not approve a report or trigger an action.

    About Attlock AI

What connects today. And what is planned.

A provider name means we intend to support that workflow, not that records already move. Ask us to confirm the status of anything you depend on before you change your process.

Available today

These are the connections and file workflows your team can use now. An export is a file handoff, not a live connection.

  • Payroll exports (CSV)

    Export

    Review approved hours, pay rules, and exceptions, then export the records for your payroll provider's upload process.

  • CSV import

    Available

    Bring guards, sites, clients, shifts, checkpoints, and incidents across with the CSV import tool, including a preflight check and rollback.

  • Shift calendar feed (iCal)

    Available

    Guards can subscribe to their own shift schedule from a calendar app through a private feed link.

  • Email and file storage

    Available

    Transactional account and report email is delivered through Resend. Incident evidence and report files are stored in Cloudflare R2.

  • Stripe billing

    Available

    Subscriptions and plan billing run through Stripe. Client invoice payments depend on your billing setup and plan.

  • Accounts and maps

    Available

    Account sign-in and role-based access are handled by Attlock account services. Site maps and guard tracking use MapTiler.

These are the connections and file workflows your team can use now. An export is a file handoff, not a live connection.

Payroll and accounting

Finance connections are the next step after a clean export. Until a connection is live, these are export workflows only.

  • QuickBooks · ADP · Paychex

    Export

    Approved hours exported for your provider's columns. Attlock does not transmit wages or file payroll taxes.

  • Xero · Gusto · Sage · Ceridian

    Planned

    Planned export and connection paths for approved hours and reviewed pay runs.

  • Accounting reconciliation

    Planned

    Planned reconciliation of invoices and payments with your accounting ledger, rather than re-keying them.

Finance connections are the next step after a clean export. Until a connection is live, these are export workflows only.

Field, safety, and enterprise

The differentiators for security operations: connecting patrol proof to doors and alarms, and keeping guards deployable. Nothing in this group is connected yet.

  • Access control

    Planned

    Planned: pair a verified checkpoint with a door event from systems such as Kisi, Brivo, Verkada, or Openpath, so a patrol proves more than a tag scan.

  • Alarm and video monitoring

    Planned

    Planned: turn an alarm or video event into an incident with site context and the nearest available guard attached.

  • SMS and team messaging

    Planned

    Planned: SMS escalation through a provider such as Twilio, and notifications into Slack or Microsoft Teams, so supervisors see alerts where they already work.

  • Enterprise single sign-on

    Planned

    Planned: single sign-on with Okta, Microsoft Entra ID, or Google Workspace for enterprise and corporate security teams.

  • Background and licence checks

    Planned

    Planned: screening and licence checks from providers such as Certn or Checkr feeding the certification records already tracked in Attlock. Registry checks depend on an authoritative source.

  • HR and workforce systems

    Planned

    Planned: connect a workforce system such as UKG, Workday, or BambooHR as the source of truth for people records.

The differentiators for security operations: connecting patrol proof to doors and alarms, and keeping guards deployable. Nothing in this group is connected yet.

Reporting and automation

Getting records to the people and systems that read them, without another manual step.

  • Client report delivery

    Planned

    Planned: deliver approved client reports into the client's Google Drive or SharePoint, and feed reporting into tools such as Power BI.

  • Signing and evidence packs

    Planned

    Planned: signed post orders and incident records through a signing provider, assembled into evidence packs for insurers and audits.

  • Zapier and Make

    Planned

    Planned: let smaller companies connect their own tools through Zapier or Make, built on the webhooks below.

  • Client-facing API

    Planned

    Planned: give larger clients an API for the approved records they are allowed to read, instead of emailed PDFs.

Getting records to the people and systems that read them, without another manual step.

For your developer. Keys, events, and a reference.

  • API keys

    Company admins create, rotate, and revoke API keys from Settings. Keys identify your company; they do not bypass its permissions.

  • Signed webhooks

    Register an endpoint for an operational event. Webhooks are signed with a per-endpoint secret, can be tested from the dashboard, and retry on failure.

  • API documentation

    An API reference is available in the dashboard alongside key management, so your developer can check the contract before building.

Webhook events you can subscribe to

7 events
  • incident_created
  • panic_triggered
  • shift_completed
  • clock_in
  • clock_out
  • checkpoint_scanned
  • visitor_logged

Tell us what you need connected. We will tell you what is real.

Bring the provider, the records, and who should see them. You get a straight answer on what works today, what stays a reviewed export, and what would need to be built.

  1. 1

    Your stack

    Name the provider and the plan you are on with them.

  2. 2

    Your records

    Which records move, in which direction, and who may see them.

  3. 3

    Your fallback

    Whether a reviewed file export works while a direct connection is assessed.

Continue the workflow.

Questions about Integrations & Exports.

What to know about getting started, supporting your team, and running your sites.

Talk to our team

No. Direct provider connections are planned. The current handoff is to review and export records for upload through your provider.

Run your security team in one place.

Schedule shifts, track patrols, and share reports.