Hidden automations that change data
Integrations that silently rewrite schedules or records create disputes nobody can trace.
Integrations
Calendars, sources, notifications, and payroll handoff in plain view.
Connection health, sync ledgers, webhook history, and notification delivery — everything an operations team needs to trust what's moving in and out of Yrka.
Evaluation focus
workforce platform integrations
- calendar sync for scheduling software
- webhook ledger workforce platform
- Slack workforce notifications
- import review tool for workforce data
- Calendars: Google, Microsoft, Apple ICS into Schedule review
- Sources: Google Drive, SharePoint/OneDrive, Notion into Resources
- Notifications: Email, Slack, SMS, Web Push delivery history
Integrations health
Integrations · Connection health
Google Calendar
Synced · 2m ago
Healthy
Slack webhook
Delivered 38/38
Healthy
Notion sources
Awaiting review
Action needed
Payroll export
Ready for review
Healthy
Generated layout — synthetic demo data.
Who it is for
- Ops leads connecting calendars, identity, and comms providers
- IT/admins reviewing webhook and delivery history
- Operators evaluating which providers are actually supported
- Calendar adapters
- 3
Google · Microsoft · ICS
- Source adapters
- 3
Drive · SharePoint · Notion
- Delivery pipes
- 5
Email · Slack · SMS · Push
Built for these realities
The pain we hear from operators
Each pain point reflects real conversations with SMB operators evaluating workforce tools today. Yrka is shaped around these realities, not generic feature checklists.
Marketing pages that imply OAuth that does not exist
'One-click integrations' for providers that actually require a custom adapter waste evaluation cycles.
No record of what was delivered, retried, or dropped
Notifications and webhooks fail quietly, then surface as missed shifts or stale data.
How teams use it
Use cases we ship for today
These are the moments this surface is built around. They map to shipped product behavior and the launch scope for this area.
Calendar and source sync
Reviewed calendar imports land in Schedule import review; source records land in Resources source review.
Notification delivery history
Email digest, Slack webhook, Slack app OAuth, SMS, and Web Push/PWA pipes each have delivery history per send.
Provider readiness messaging
Integrations surface tells you which providers are ready, which need setup, and which are not supported before any setup attempt.
Why Yrka here
What makes this different
Differentiators map to shipped product behavior. They are the reasons buyers pick this surface after comparing alternatives.
Review first, sync second
Import Center owns hands-on intake; Integrations owns movement, health, connection state, and delivery history.
Setup is explicit
Live provider setup depends on customer authorization, provider apps, credentials, and supported adapters — never assumed.
Auditable delivery
Every webhook and notification leaves a trail you can review when a thing did not happen.
How it flows
A workflow that mirrors how operators actually run the day
Three steps, three responsibilities.
- 01
Configure
Hook up provider credentials, choose the calendars or sources, and set delivery pipes.
- 02
Review
Imports and sources stage in a review queue before they reach Schedule or Resources.
- 03
Observe
Watch connection health, sync jobs, webhook ledgers, and delivery history in plain view.
What's inside
Integrations highlights
Calendar sync
Google and Microsoft Calendar imports staged for Schedule review.
Source sync
Google Drive, SharePoint/OneDrive, and Notion staged for Resources review.
Delivery pipes
Email digest, Slack webhook, Slack OAuth, SMS, and Web Push with delivery history.
Payroll bridge
Payroll handoff with setup review, provider readiness, and export evidence; no submission claims.
SSO readiness
Google and Microsoft sign-in policy diagnostics with allowed-domain and pending-access review.
Health and ledgers
Connection registry, sync jobs, and webhook ledgers visible without exposing secrets.
Review-first by design
Import Center owns hands-on intake. Integrations owns movement, health, connection state, source status, and delivery history — so nothing flips on silently.
Setup that stays explicit
Live provider use depends on customer authorization, provider credentials, provider-app approval, and supported adapters. We surface each step instead of hiding it.
Scope
What's included, what's intentionally out of scope
Yrka maps every feature to its product claim so commercial conversations stay honest.
Included
- Connection registry
- Sync job ledgers
- Webhook ledgers
- Notification delivery history
- Reviewed Google/Microsoft/Apple ICS calendar import profiles
- Live Google and Microsoft Calendar sync into Schedule import review when provider OAuth credentials, customer authorization, and selected calendar/date-window setup are configured
- Reviewed Notion and Google Drive source export profiles
- Live Google Drive, SharePoint/OneDrive, and Notion source sync when provider OAuth credentials, customer authorization, and selected source ids are configured
- Server-configured email digest, Slack webhook, Slack app OAuth, Twilio SMS, and Web Push/PWA notification pipes
- Google and Microsoft sign-in policy diagnostics with allowed-domain and pending-access review gates
- Provider-gated payroll bridge setup-review and time-export handoff evidence without payroll submission
- Source readiness status
- Provider-gated setup state
Boundaries
- Live OAuth unless configured
- Guaranteed third-party provider uptime
- Provider contract management
- Custom provider apps by default
Related
Where this fits in the platform
Trust and security
Real controls. Honest scope. Customer in charge.
Supabase auth, organization scoping, row level security, role checks, private file storage, signed URLs, audit events, AI boundaries, and operations runbooks — described as built, not as promised.
ExploreScheduling
Plan coverage. Publish with confidence.
Build the week from coverage in. Rotate templates, fill open shifts with manager-approved offers, import schedule files, and publish only the shifts that are ready.
ExploreCommunications
Messages, boards, and follow-up that match the workflow.
Direct messages, board announcements, app notifications, and review-required inbox work — each distinct, all connected to the operations they belong to.
ExploreQuestions
Common buyer questions
We surface the questions buyers actually ask — trial, support, export, mobile, payroll, provider, AI, and trust scope — in plain language.
Are provider integrations live by default?
Live calendar, source, notification, and payroll-bridge pipes turn on after customer authorization, provider credentials, app approval, and adapter support are in place. We show what is ready at each step.
How does the trial work?
Start with a 30-day card-required trial. Cancel anytime from the Stripe customer portal. Workspaces stay available for export or reactivation for 30 days after paid access ends.
Does Yrka process payroll or file taxes?
No. Yrka covers time tracking, scheduling, payroll-prep exports, and provider handoff. Customers stay in charge of payroll processing, tax filing, legal, and HR decisions.
What does mobile look like?
Responsive web and an installable PWA cover employee time entry, scheduling, resources, tasks, messages, and profile review. Employees see scoped offline read context plus queued supported writes with clear sync states.
Can we export our data?
Yes. Payroll-prep exports, schedule and time reports, and employee data exports are part of the core product. Customer data remains exportable for 30 days after paid access ends unless an earlier deletion is requested.
Ready to run the day on Yrka?
Start a 30-day trial in minutes, or book a working session to walk through the rollout with someone who has done this before.