Three ways to integrate
Pick the depth that fits your needs — start light, grow when ready.
Outbound — skaills enriches Bob
Planned~2 weeks. Bob's API is clean and the first connector stands up fast.
Bidirectional — Bob drives, skaills assesses
Planned~5-7 weeks. Bob webhooks + custom-field mapping + SSO if applicable.
HiBob Marketplace — skaills as a partner
Roadmap4-5 months including HiBob partner certification and security review.
What this looks like in practice
Concrete flows triggered by events in HiBob.
| Trigger in HiBob | What skaills does | What flows back to HiBob |
|---|---|---|
| Candidate applies to a position posted in Bob Hiring | skaills generates a personalized evaluation link and sends it to the candidate | Score + competency profile + recommendation appear as a custom field on the candidate record in Bob Hiring |
| Employee finishes a Bob review cycle (performance + 360) | skaills runs competency evaluation + AI-Readiness + Growth Plan + Career Path | Plan summary, suggested paths, and learning recommendations appear as custom fields on the Bob profile |
| Bob engagement / pulse survey closes | skaills correlates with multi-dimensional climate survey and generates a prioritized action plan | Consolidated report delivered to the HR sponsor; engagement signal appears as a metric linked to the Bob dashboard |
| CHRO launches a 12-24 month transformation initiative | skaills generates an Org Transformation Plan with aggregated Bob data (structure, comp, surveys, attrition) | CHRO-grade roadmap with capability heatmap, transformation tracks, and 30/90/180/365 KPIs delivered as a skaills dashboard |
Technical architecture
The integration uses Bob's official REST API. Authentication via a service-user token generated in your Bob tenant (scope limited to the necessary endpoints). Bob webhooks (in bidirectional mode) land at a dedicated skaills Cloud Function (`hibobWebhook`) with signature verification. skaills never stores the token outside Google Secret Manager. All skaills-side logic is serverless — no infrastructure for your team to run. Data in transit via HTTPS (TLS 1.2+) and at rest encrypted.
Implementation timeline
1
Week 1
Define which flows are in scope (Hiring, Performance, surveys, transformation), what data travels, identify HR sponsor, customer-side Bob technical owner, and skaills team.Kickoff and scope
Deliverable:Signed scope document
2
Weeks 2-3
Generate Bob service-user token, configure custom fields where skaills outputs will appear, configure webhooks if bidirectional, first E2E test with a synthetic candidate/employee.Technical setup
Deliverable:E2E test passing with synthetic data
3
Week 4
Activate with a real team (Hiring or Performance), 5-15 real people complete the flow. Monitor completion, latency, score quality, manager and HR satisfaction.Controlled pilot
Deliverable:Pilot report with real metrics
4
Week 5
Roll out to the rest of the organization by team or BU. Internal documentation for HR and IT. Handoff session. Ongoing support at the agreed cadence (typically monthly).Rollout and handoff
Deliverable:Integration in production + runbook delivered
For global customers with multi-country Bob tenants, add 1-2 weeks for data-residency rules. For HiBob Marketplace listing, add ~4 additional months for certification.
