.png)
Culture Amp Integration Guide
Connect Culture Amp employee, survey, and people analytics data with enterprise systems through REST APIs, scheduled workflows, and controlled data synchronization.
Culture Amp integration options at a glance
Culture Amp’s primary integration mechanism is its documented REST API, which supports employee, survey, response, and people-data use cases subject to the API product, tenant, subscription, and permissions. Martini can consume these APIs with tenant-provisioned bearer credentials, transform JSON payloads, manage pagination, and coordinate scheduled synchronization workflows. Culture Amp may provide product-specific export or reporting capabilities, but a universal bulk API and general-purpose file API were not confirmed. General webhook coverage for all business objects is also not confirmed, so scheduled polling with checkpoints is often the safer design. Martini can additionally expose a normalized REST API for internal consumers and write extracted data to supported databases or analytics platforms.
| Integration point | Supported by Culture Amp? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Synchronize People or Employees, Surveys, Survey responses, Questions, Demographics, and Reports with HRIS, warehouse, or reporting applications. | Martini can consume Culture Amp REST endpoints, add bearer credentials, paginate requests, transform JSON, apply business rules, and expose normalized APIs. |
| Webhooks / outbound callbacks | Limited | Selected product or tenant events may be available, but general-purpose coverage for employee, survey, and response changes was not confirmed. | Martini can receive webhook-style notifications when Culture Amp provides the required callback, then retrieve the current resource and process it idempotently. |
| Bulk / async / batch APIs | Limited | Product-specific exports or reporting-oriented bulk capabilities may support larger survey or people-data extracts; universal coverage was not confirmed. | Martini can orchestrate supported exports or use paginated REST extraction with checkpoints, bounded concurrency, retries, and backoff. |
| Authentication | Yes | Culture Amp API access uses administrator-provisioned credentials or tenant-specific bearer tokens, with access governed by tenant permissions. | Martini stores tokens in environment secrets and applies authentication configuration without embedding credentials in workflows or mappings. |
| Scheduled synchronization | Yes | Scheduled polling is appropriate when the required Culture Amp event is not available as a webhook or callback. | Martini scheduler-triggered workflows can retrieve incremental data, persist cursors or timestamps, and reconcile incomplete runs. |
| JSON data exchange | Yes | Culture Amp REST payloads are handled as JSON for employee, survey, response, demographic, and report integrations. | Martini can parse, validate, map, transform, and route JSON payloads between Culture Amp and downstream systems. |
| Database or analytics access | No | Culture Amp does not expose a customer database for direct SQL access; analytics data should come from documented APIs or supported exports. | Martini can write extracted Culture Amp data to supported databases or analytics platforms without requiring direct Culture Amp database access. |
| File / attachment APIs | Not confirmed | No general-purpose Culture Amp file or attachment API was confirmed; product-specific exports require validation. | Martini can process a supported export if one is supplied, but the integration should not assume a universal Culture Amp file API. |
How Culture Amp exposes data and business events
Culture Amp REST APIs
Culture Amp’s documented REST APIs are the primary integration mechanism for supported employee, survey, response, and people analytics use cases. Exact endpoints, schemas, permissions, and available objects depend on the selected API product, tenant configuration, and subscription.
Martini implementation pattern
Martini implementation pattern: Martini authenticates with a tenant-provisioned bearer token, invokes the required REST endpoint, handles pagination and response validation, transforms Culture Amp JSON into a canonical model, and writes the result to the target system. Scheduled workflows are appropriate when no confirmed event callback exists.
Implementation sequence
Culture Amp webhook-style notifications
A general-purpose webhook framework covering all major Culture Amp objects and changes was not confirmed. Specific product or tenant capabilities must be validated before designing a real-time flow for employee updates, survey completion, or report availability.
Martini implementation pattern
Martini implementation pattern: when the required Culture Amp callback is available, Martini receives the notification, authenticates and validates it, retrieves the authoritative resource from the Culture Amp API, and processes it through an idempotent workflow. If the event is unavailable, a scheduler-triggered polling workflow uses a cursor, watermark, or overlap window instead.
Implementation sequence
Culture Amp scheduled extraction
Scheduled synchronization is a practical fallback for data that does not have confirmed webhook coverage. It can support employee reconciliation, survey-result extraction, and reporting exports using documented REST endpoints or validated product-specific export capabilities.
Martini implementation pattern
Martini implementation pattern: a scheduler starts a workflow that reads the last successful cursor or timestamp, retrieves bounded pages, applies overlap and deduplication rules, writes data to the target, and records successful and failed items for reconciliation.
Implementation sequence
Common Culture Amp integration patterns
Pattern 1: Synchronize employees from an HRIS to Culture Amp
When to use this pattern
Use this pattern when Culture Amp needs current workforce, organizational, and employment data from Workday, BambooHR, HiBob, ADP Workforce Now, Personio, or Rippling. The workflow should support new hires, updates, manager changes, organizational changes, and employee deactivation without deleting historical survey data.
Integration direction
Example Mapping
| Culture Amp Field | Canonical Field | Target Field |
|---|---|---|
| employeeId | person.externalId | People or Employees identifier |
| employmentStatus | person.lifecycleStatus | employment status |
| department | organization.department | department |
| managerId | organization.managerExternalId | manager identifier |
Martini implementation pattern
Martini runs a scheduled or source-triggered workflow, retrieves changed HRIS employees, validates required identifiers, maps organizational fields, applies rules for inactive employees and missing managers, and submits idempotent Culture Amp updates. Failed records are separated from transient API failures so retries do not repeat successful writes.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- secrets management
- error handling
Pattern 2: Load Culture Amp survey results into a warehouse
When to use this pattern
Use this pattern when approved survey, response, question, demographic, or report data must be consolidated for governed analytics. The design should preserve Culture Amp identifiers and privacy rules while avoiding unnecessary export of individual-level response content.
Integration direction
Example Mapping
| Culture Amp Field | Canonical Field | Target Field |
|---|---|---|
| surveyId | survey.externalId | survey_id |
| questionId | response.questionExternalId | question_id |
| demographic | response.segment | segment |
| reportValue | metric.value | metric_value |
Martini implementation pattern
A scheduled Martini workflow identifies completed or extractable surveys, retrieves paginated results, normalizes changing question and demographic structures, applies aggregation and access rules, and upserts governed warehouse tables. Checkpoints, overlap windows, retries, and reconciliation counts make reruns safe and observable.
Martini capabilities used
- scheduled workflows
- API consumption
- pagination orchestration
- data mapping
- privacy business rules
- database integration
- error handling
Pattern 3: Expose a normalized Culture Amp API
When to use this pattern
Use this pattern when internal applications need selected Culture Amp people or survey data without receiving Culture Amp credentials or depending on vendor-specific response formats. It provides a controlled boundary for authorization, filtering, and schema stability.
Integration direction
Example Mapping
| Culture Amp Field | Canonical Field | Target Field |
|---|---|---|
| People.id | employee.id | employeeId |
| People.department | employee.organizationUnit | organizationUnit |
| Survey.status | survey.lifecycleState | status |
| Report.value | metric.value | value |
Martini implementation pattern
Martini exposes a REST API that authenticates internal callers, validates query parameters, invokes the required Culture Amp endpoint, filters sensitive fields, transforms the response to a stable internal schema, and returns controlled errors. Caching or checkpointed retrieval can be added where the use case permits.
Martini capabilities used
- API exposure
- API consumption
- authentication and authorization
- data transformation
- validation
- error handling
Pattern 4: Orchestrate employee lifecycle and survey updates
When to use this pattern
Use this pattern when an employee lifecycle change must be coordinated across an HRIS, Culture Amp, identity tooling, and collaboration applications. Because universal Culture Amp event coverage is not confirmed, the source trigger may be an HRIS event or a scheduled reconciliation workflow.
Integration direction
Example Mapping
| Culture Amp Field | Canonical Field | Target Field |
|---|---|---|
| employmentStatus | lifecycle.status | Culture Amp employee status |
| startDate | lifecycle.effectiveDate | onboarding attribute |
| managerId | organization.managerExternalId | manager identifier |
| employeeId | identity.subject | Okta or notification reference |
Martini implementation pattern
Martini receives or polls the authoritative lifecycle change, evaluates effective dates and status rules, updates Culture Amp and other approved systems in a controlled sequence, and records each step. Retries are scoped to failed operations, while reconciliation detects partial completion and prevents duplicate updates.
Martini capabilities used
- workflow orchestration
- scheduled triggers
- API consumption
- conditional routing
- data mapping
- business rules
- retries and reconciliation
Applications commonly integrated with Culture Amp
Culture Amp commonly participates in employee-data, identity, collaboration, and reporting architectures. The exact integration model may be native, partner-based, or custom API orchestration, so tenant capabilities and product-specific support should be confirmed before implementation.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Workday | Synchronize employee profiles, organizational hierarchy, managers, and employment status used in Culture Amp surveys. | Workday → Martini → Culture Amp | Martini schedules or receives the available Workday change feed, maps employee identifiers and organizational attributes to Culture Amp’s people model, applies status and deactivation rules, and records reconciliation outcomes. |
| BambooHR | Keep employee, department, location, and lifecycle data current for engagement and employee surveys. | BambooHR → Martini → Culture Amp | A Martini workflow retrieves changed BambooHR employees, validates required fields, transforms the payload to Culture Amp’s documented REST representation, and retries transient failures with checkpointed progress. |
| HiBob | Transfer employee, manager, department, and location data into Culture Amp. | HiBob → Martini → Culture Amp | Martini consumes the HiBob API, normalizes organizational attributes, performs idempotent Culture Amp updates, and routes validation failures to a reconciliation queue or report. |
| ADP Workforce Now | Synchronize workforce records and employment changes with Culture Amp’s people data. | ADP Workforce Now → Martini → Culture Amp | Martini orchestrates scheduled extraction, maps source employee identifiers and employment status, applies privacy and deactivation rules, and persists source-to-target synchronization state. |
| Personio | Provide employee lifecycle and organizational data for Culture Amp surveys. | Personio → Martini → Culture Amp | A workflow retrieves Personio changes, transforms department, location, manager, and employment fields, invokes Culture Amp REST endpoints, and produces a run-level reconciliation summary. |
| Rippling | Synchronize employee changes and organizational attributes with Culture Amp. | Rippling → Martini → Culture Amp | Martini consumes the available Rippling and Culture Amp APIs, uses stable employee identifiers for upserts, applies business rules for inactive employees, and retries rate-limited requests. |
| Okta | Support centralized identity management, SSO, and access-related user lifecycle processes for Culture Amp users. | Okta → Martini → Culture Amp | Where an API-based orchestration is required, Martini coordinates identity and Culture Amp administration workflows, keeps credentials in secrets, and separates identity operations from survey-data synchronization. |
| Slack | Deliver selected engagement or survey-related notifications and support participation workflows where the applicable Culture Amp features and events are available. | Culture Amp → Martini → Slack | Martini retrieves or receives the supported Culture Amp event or status, applies authorization and message rules, and posts a controlled notification to Slack while avoiding sensitive individual response content. |
How to build a Culture Amp integration in Martini
Objective
Establish access to the selected Culture Amp API and any source or target applications without embedding credentials in integration logic.
Instructions in Martini
- Confirm the required Culture Amp API, tenant permissions, and available objects.
- Store the Culture Amp bearer token or API credential in Martini secrets or environment configuration.
- Configure the source and target API authentication independently.
Objective
Select a trigger that matches the confirmed Culture Amp capabilities and required freshness.
Instructions in Martini
- Use a scheduler for polling and incremental synchronization when event coverage is not confirmed.
- Use a Culture Amp callback only after validating that the required event is available.
- Use an HRIS event when employee lifecycle data originates in the HRIS.
Objective
Read the authoritative Culture Amp or source-system data while preserving extraction state and handling bounded requests.
Instructions in Martini
- Retrieve the selected People, Surveys, Survey responses, Questions, Demographics, or Reports resource.
- Handle pagination, cursors, timestamps, and overlap windows.
- Persist progress so a failed run can resume safely.
Objective
Coordinate retrieval, transformation, business rules, target writes, and reconciliation as a maintainable Martini workflow.
Instructions in Martini
- Separate transient API failures from authorization, validation, and business-rule failures.
- Use conditional routing for inactive employees, incomplete surveys, and privacy-sensitive data.
- Keep source and target identifiers available throughout the workflow.
Objective
Convert Culture Amp and adjacent-system payloads into a canonical model that remains resilient to changing survey structures.
Instructions in Martini
- Map stable identifiers, lifecycle status, organizational attributes, questions, answers, and report metrics.
- Validate required fields and tolerate additive fields where appropriate.
- Avoid positional mappings for questions and demographic dimensions.
Objective
Protect employee privacy and ensure that only approved, meaningful data is propagated.
Instructions in Martini
- Enforce aggregation, minimum-group-size, and access rules for survey data.
- Define how inactive or departed employees are deactivated, archived, or retained.
- Restrict sensitive response content from operational logs.
Common Culture Amp data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| People or Employees | Synchronize workforce members, identifiers, employment status, managers, departments, locations, and organizational attributes. | Workday, BambooHR, HiBob, ADP Workforce Now, Personio, Rippling, data warehouses | Martini retrieves or receives source changes, maps stable identifiers and organizational fields, applies lifecycle rules, and performs idempotent Culture Amp updates or reconciliation. |
| Surveys | Identify engagement, pulse, onboarding, exit, or other survey programs and their lifecycle status. | Data warehouses, reporting platforms, internal APIs | Martini retrieves survey metadata, filters surveys ready for extraction, preserves source identifiers, and routes selected data to downstream workflows. |
| Survey responses | Capture submitted answers or response data for approved reporting and analysis. | Data warehouses, analytics platforms, governed reporting stores | Martini paginates response extraction, applies privacy and aggregation rules, normalizes answer structures, and restricts sensitive payloads from operational logs. |
| Questions | Describe survey questions and answer definitions needed to interpret response data. | Data warehouses, analytics models, reporting applications | Martini preserves question identifiers and metadata, avoids positional mappings, and versions transformations when survey structures change. |
| Demographics | Represent organizational or demographic dimensions used to segment survey results. | Reporting stores, analytics platforms, HR data environments | Martini maps approved dimensions, validates permitted values, and applies tenant privacy and minimum-group-size rules before downstream publication. |
| Reports | Provide aggregated survey or engagement results for analysis and operational reporting. | Data warehouses, BI platforms, management reporting applications | Martini retrieves available report data, tracks extraction state, normalizes report structures, and writes governed aggregates to target systems. |
Authentication and security considerations
Tenant-provisioned credentials
Culture Amp API access commonly uses administrator-provisioned API credentials or bearer tokens. The exact authentication method and permissions should be confirmed for the selected API product and tenant.
Secrets and permissions
Store Culture Amp credentials in Martini environment secrets rather than in workflows, mappings, or logs. Limit credentials to the tenant permissions and data required by the integration.
Survey privacy
Survey responses and demographic data may contain sensitive employee information. Restrict raw response access, preserve Culture Amp aggregation rules, and avoid writing individual response content to operational logs.
Operational considerations for Culture Amp integrations
Pagination and rate limits
Design for paginated responses, bounded concurrency, confirmed quotas, HTTP 429 responses, and Retry-After headers. Persist cursors, timestamps, or page state for resumable extraction.
Idempotency and reconciliation
Use stable Culture Amp identifiers and source-system keys for upserts or existence checks. Retain synchronization status, last successful operation, error state, and retry count.
Schema changes
Survey questions, answer definitions, demographics, and report structures can vary. Preserve source metadata, avoid positional mappings, validate required fields, and version mappings when necessary.
Tenant and privacy differences
API access, available objects, authentication, and data may vary by plan, region, tenant configuration, and administrator permissions. Confirm the required endpoints before finalizing the design.
Why use Martini instead of scripts or point-to-point integrations?
Maintainable orchestration
Martini separates API access, workflow orchestration, mapping, business rules, and error handling instead of concentrating all behavior in a one-off script.
Reliable synchronization
Scheduled workflows can manage pagination, checkpoints, retries, overlap windows, idempotent writes, and reconciliation across Culture Amp and enterprise systems.
Controlled access
Martini can expose a normalized API so internal applications do not need Culture Amp credentials or vendor-specific response formats. Authorization, filtering, and privacy rules can be applied at the integration boundary.
Reusable integration assets
API consumption, transformations, validation, and target-writing logic can be reused across HRIS synchronization, survey-result extraction, and lifecycle orchestration without creating separate point-to-point scripts.
Frequently asked questions
Culture Amp can be integrated primarily through its documented REST APIs for People or Employees, Surveys, Survey responses, Questions, Demographics, and Reports. Enterprise workflows can use scheduled extraction, validated product-specific exports, or selected webhook-style notifications where available. Martini can authenticate, paginate, transform JSON, apply privacy and business rules, synchronize data with HRIS and warehouse systems, and expose normalized APIs.
Yes. Martini can integrate with Culture Amp by consuming its documented REST APIs, using tenant-provisioned bearer credentials, orchestrating scheduled synchronization workflows, transforming Culture Amp JSON, and writing to enterprise targets. Webhook handling can be used only if the required Culture Amp event is available for the relevant tenant and product.
No. A dedicated Culture Amp connector is not required. Martini can use Culture Amp’s confirmed native integration mechanisms, primarily its REST APIs and tenant-provisioned authentication, with scheduled workflows, mappings, transformations, and optional callbacks where specifically supported.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Culture Amp. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Culture Amp, cloud infrastructure, or other third-party systems depending on subscriptions, usage, and deployment model.
Use the documented Culture Amp REST APIs as the primary method. Scheduled polling is appropriate when real-time event coverage is unavailable or unconfirmed. Product-specific exports or bulk capabilities should be validated for the tenant, and a general-purpose file API, GraphQL API, SOAP API, or direct database access should not be assumed.
A general-purpose webhook framework covering all major Culture Amp objects and changes was not confirmed. Specific event notifications may be available for particular products or tenants, but the required event must be validated. Otherwise, Martini can poll REST endpoints on a schedule using timestamps, cursors, overlap windows, and idempotent processing.
Martini can run scheduled or source-triggered workflows that retrieve paginated Culture Amp data, persist cursors or timestamps, map payloads to a canonical model, apply privacy and lifecycle rules, and upsert target records using stable identifiers. Checkpoints, retries, and reconciliation reports support reliable incremental or controlled full synchronization.
Martini can distinguish transient failures, rate limiting, authorization problems, validation errors, and business-rule failures. Workflows can use bounded concurrency, exponential backoff, Retry-After handling, persisted checkpoints, and idempotent writes based on stable Culture Amp and source identifiers. Reconciliation data can show created, updated, skipped, rejected, and pending records.
Related Martini documentation
Workflows
Data
Integrate Culture Amp with Martini
Use Martini to connect Culture Amp with HRIS platforms, warehouses, reporting applications, and internal APIs through secure workflows, REST API orchestration, data transformation, and reliable synchronization.