.png)
Five9 Integration Guide
Integrate Five9 contact-center data and administration with enterprise applications through its SOAP Web Services API, selected REST APIs, reporting interfaces, and scheduled workflows.
Five9 integration options at a glance
Five9 integrations commonly use the documented SOAP Web Services API for administrative, configuration, reporting, and contact-center operations, together with REST APIs for selected products and capabilities. Authentication is permission-controlled, with SOAP and REST security patterns managed separately; OAuth 2.0 may apply to specific REST services. Five9 does not have a confirmed universal webhook model, so event-driven designs should be validated for the selected product and may use scheduled polling or reporting exports instead. Martini can consume Five9 SOAP and REST endpoints, store credentials as managed secrets, transform XML and JSON payloads, orchestrate incremental synchronization, and expose APIs for internal applications.
| Integration point | Supported by Five9? | Common use cases | How Martini supports it |
|---|---|---|---|
| SOAP Web Services API | Yes | Five9's documented SOAP Web Services API supports selected administrative, configuration, reporting, and contact-center operations through WSDL-defined services. | Martini can consume the WSDL-defined SOAP service, construct requests, parse XML responses and faults, map results into canonical models, and orchestrate downstream writes. |
| REST APIs | Limited | Five9 provides REST APIs for selected products and capabilities. Endpoint coverage, tenant availability, permissions, and authentication vary by service. | Martini can consume documented Five9 REST resources, manage API configuration and secrets, transform JSON payloads, and apply workflow-level validation and retry policies. |
| Bulk / async / batch APIs | Limited | Some Web Services API operations may support administrative or reporting-scale processing, including operations that return job or report identifiers. | Martini can submit supported jobs, poll for completion, apply timeouts, process pages or result sets, and persist checkpoints to support resumable extraction. |
| Reporting and export interfaces | Limited | Reporting data can be extracted for performance, campaign, agent, queue, disposition, and operational analytics when the tenant exposes the required reporting or export capability. | Martini can schedule extraction, normalize and deduplicate results, and load a warehouse or analytics platform through its supported API or database interface. |
| Webhooks / outbound callbacks | Not confirmed | A universal Five9 webhook mechanism covering all contact-center events was not confirmed. Product-specific notifications, callbacks, or streaming options must be verified. | Martini can receive webhook-style notifications when a selected Five9 product explicitly supports them; otherwise it can use scheduled polling, incremental retrieval, or documented exports. |
| Authentication | Yes | Five9 API access is authenticated and permission-controlled. SOAP and REST authentication patterns may differ, and OAuth 2.0 details must be confirmed for the selected REST service. | Martini can isolate Five9 credentials, tokens, domains, endpoints, and WSDL settings in environment-managed secrets and use least-privilege integration identities. |
| GraphQL APIs | Not confirmed | No official Five9 GraphQL API reference was identified in the supplied research. | Martini can consume GraphQL APIs generally, but a Five9 GraphQL integration should not be designed without confirmed Five9 documentation. |
| File / attachment APIs | Not confirmed | A general-purpose Five9 file or customer-attachment API was not confirmed. Arbitrary file upload to contact or interaction records should not be assumed. | Martini can process files through supported platform capabilities, but a Five9 file exchange should use only a specifically documented Five9 module or export mechanism. |
How Five9 exposes data and business events
Five9 SOAP Web Services API
Five9's Web Services API is the clearest publicly documented integration mechanism. It provides WSDL-defined SOAP operations for selected administrative, configuration, reporting, and contact-center functions. Available operations depend on the tenant, API version, permissions, and enabled modules.
Martini implementation pattern
Martini implementation pattern: Martini consumes the applicable WSDL-defined service from a workflow, stores the Five9 domain and credentials as managed configuration, serializes XML requests, parses SOAP responses and faults, maps the result into a canonical model, and invokes downstream APIs or data stores.
Implementation sequence
Five9 REST APIs
Five9 provides REST APIs for selected products and capabilities. REST coverage is not necessarily equivalent to the SOAP Web Services API, and endpoint availability and authentication vary by product, tenant, package, and developer access.
Martini implementation pattern
Martini implementation pattern: Martini consumes the documented REST resource, obtains or refreshes the required token where applicable, validates response status and payload shape, transforms JSON into the target model, and applies rate-aware retries and checkpointing.
Implementation sequence
Five9 Reporting and Batch Retrieval
Five9 reporting or Web Services API operations may support larger-scale retrieval, batch processing, or asynchronous jobs. The job model, pagination, limits, and completion behavior must be confirmed for the selected operation.
Martini implementation pattern
Martini implementation pattern: Martini starts a supported report or batch request, records the job or report identifier, polls with bounded intervals, handles timeout and failure states, processes pages or result files, and writes a durable extraction checkpoint.
Implementation sequence
Five9 Notifications and Polling
A universal Five9 webhook model covering all contact-center events was not confirmed. Product-specific notifications, callbacks, or streaming mechanisms must be verified; where they are unavailable, scheduled polling or incremental reporting retrieval can identify changes.
Martini implementation pattern
Martini implementation pattern: When a supported notification exists, Martini can receive and validate it before retrieving the current Five9 object. Otherwise, a scheduler workflow queries the relevant API or report using timestamps, status fields, or vendor-supported cursors and then applies idempotent processing.
Implementation sequence
Common Five9 integration patterns
Pattern 1: Synchronize Five9 Contacts with Salesforce
When to use this pattern
Use this pattern when agents and outbound campaigns require Five9 Contacts to reflect Salesforce leads, contacts, or customer records. The flow can be bidirectional, but field ownership and the authoritative source for each attribute should be defined before implementation.
Integration direction
Example Mapping
| Five9 Field | Canonical Field | Target Field |
|---|---|---|
| Salesforce Contact.Id | customer.externalId | Five9 Contact.externalId |
| Salesforce Contact.Phone | customer.primaryPhone | Five9 Contact.phone |
| Salesforce Contact.Email | customer.email | Five9 Contact.email |
| Five9 Disposition | interaction.outcome | Salesforce Activity.status |
Martini implementation pattern
A scheduled or supported event-triggered Martini workflow retrieves Salesforce changes, validates required contact data, detects duplicates using stable identifiers, and calls the appropriate Five9 REST or SOAP operation. A reverse workflow retrieves Five9 Dispositions or interaction outcomes, maps them to Salesforce activity statuses, retries transient failures, and sends non-retryable records to an exception process.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- error handling
- scheduled execution
Pattern 2: Route Five9 interaction outcomes to ServiceNow
When to use this pattern
Use this pattern when selected Five9 interactions require incidents, cases, or service tasks. Because universal Five9 event coverage was not confirmed, the trigger may be a documented notification, a reporting API, or a scheduled incremental query.
Integration direction
Example Mapping
| Five9 Field | Canonical Field | Target Field |
|---|---|---|
| Five9 Contact | customer.reference | ServiceNow Caller |
| Five9 Disposition | interaction.outcome | ServiceNow Category or State |
| Five9 Agent | interaction.owner | ServiceNow Assigned to |
| Five9 Campaign | interaction.program | ServiceNow Assignment group |
Martini implementation pattern
Martini retrieves the relevant Five9 interaction or reporting data, filters records by disposition and business priority, resolves the customer and agent context, and creates or updates ServiceNow records. Idempotency keys or stored source identifiers prevent duplicates, while authentication, permission, validation, and downstream failures are classified separately.
Martini capabilities used
- workflow orchestration
- API consumption
- data mapping
- conditional routing
- idempotency
- error handling
Pattern 3: Provision Five9 agents and skills from Workday
When to use this pattern
Use this pattern when joiner, mover, and leaver changes in Workday should drive selected Five9 administration. The exact administrative operations must be confirmed for the tenant and the integration identity should have only the required permissions.
Integration direction
Example Mapping
| Five9 Field | Canonical Field | Target Field |
|---|---|---|
| Workday Worker.ID | worker.externalId | Five9 Agent.externalId |
| Workday Worker.Name | worker.displayName | Five9 Agent.name |
| Workday Worker.Status | worker.lifecycleStatus | Five9 Agent.status |
| Workday Organization | worker.organization | Five9 Skill or Queue assignment |
Martini implementation pattern
A Martini workflow retrieves approved Workday changes, validates lifecycle and organizational attributes, applies least-privilege rules, and sequences dependent Five9 Agent, Skill, or Queue operations. Each operation is logged with the source identifier and result; transient service errors are retried, while permission and validation failures are routed for remediation.
Martini capabilities used
- scheduled workflows
- SOAP and REST API consumption
- validation
- business rules
- sequencing
- audit and error handling
Pattern 4: Load Five9 reporting data into Snowflake
When to use this pattern
Use this pattern when contact-center performance, campaign, agent, queue, and disposition data must be consolidated for enterprise reporting. Select the reporting, SOAP, REST, or export interface supported by the specific Five9 tenant and reporting product.
Integration direction
Example Mapping
| Five9 Field | Canonical Field | Target Field |
|---|---|---|
| Five9 Agent | contactCenter.agent | Snowflake agent_id |
| Five9 Campaign | contactCenter.campaign | Snowflake campaign_id |
| Five9 Queue | contactCenter.queue | Snowflake queue_id |
| Five9 Disposition | interaction.outcome | Snowflake disposition_code |
Martini implementation pattern
A scheduled Martini workflow defines a time window, submits or retrieves the supported Five9 report, polls asynchronous jobs when required, processes pages, normalizes time zones, and deduplicates rows using stable identifiers and extraction windows. It then loads Snowflake and advances the checkpoint only after successful persistence.
Martini capabilities used
- scheduler triggers
- workflow orchestration
- SOAP and REST API consumption
- pagination and checkpointing
- data transformation
- retry handling
Applications commonly integrated with Five9
Five9 can be integrated with customer, service, workforce, financial, collaboration, and analytics applications. The exact Five9 object coverage and direction should be confirmed for the tenant, enabled modules, API product, and required operation.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize leads, contacts, customer context, campaign data, dispositions, and follow-up activities used by contact-center agents. | Salesforce → Martini → Five9 | Martini can retrieve Salesforce changes, validate and deduplicate customer data, map it to Five9 Contacts or Campaigns, and invoke the applicable Five9 REST or SOAP operation. A complementary workflow can retrieve Five9 Dispositions or interaction outcomes and update Salesforce with explicit status mappings and retry handling. |
| ServiceNow | Create or update incidents, cases, and service tasks when a Five9 interaction requires operational follow-up. | Five9 → Martini → ServiceNow | Martini can extract qualifying Five9 interaction, Contact, Agent, Campaign, and Disposition data through the applicable reporting or API interface, apply routing rules, and write normalized records to ServiceNow. Non-retryable validation and permission failures can be routed to an exception workflow. |
| Microsoft Dynamics 365 | Provide customer and account context to agents while synchronizing contact-center outcomes with customer records. | Microsoft Dynamics 365 → Martini → Five9 | A Martini workflow can synchronize selected Dynamics 365 customer changes to Five9 and return Five9 outcomes to Dynamics 365. Stable identifiers, field ownership, timestamp windows, and disposition mappings can be maintained to prevent duplicate updates. |
| Zendesk | Associate calls or digital interactions with customer profiles and support tickets. | Five9 → Martini → Zendesk | Martini can retrieve available Five9 interaction or reporting data, resolve the associated Contact, normalize disposition and agent information, and create or update Zendesk tickets. The workflow can use idempotency keys or source identifiers when retrying writes. |
| Workday | Use employee and organizational changes to drive selected Five9 agent, user, role, skill, or campaign administration updates. | Workday → Martini → Five9 | Martini can receive or schedule Workday extracts, validate joiner, mover, and leaver changes, enforce least-privilege rules, sequence dependent administrative operations, and record each Five9 provisioning result for reconciliation. |
| NetSuite | Connect customer or account information with contact-center activity supporting order, billing, and customer-service processes. | NetSuite → Martini → Five9 | Martini can synchronize selected NetSuite customer data to Five9 and route relevant Five9 outcomes back to NetSuite. Business rules can limit financial or personal data exposure, while retries and identifier mappings support reliable reconciliation. |
| Snowflake | Centralize Five9 reporting, campaign, agent, queue, and disposition data for enterprise analytics. | Five9 → Martini → Snowflake | A scheduled Martini workflow can invoke the appropriate Five9 reporting, REST, SOAP, or export interface, process pages or asynchronous report jobs, normalize timestamps, deduplicate results, and load Snowflake using the target platform's supported interface. |
| Microsoft Teams | Coordinate collaboration and escalation notifications around contact-center activity. | Five9 → Martini → Microsoft Teams | Where the selected Five9 product exposes suitable interaction or reporting data, Martini can evaluate business rules and publish controlled notifications to Teams. The workflow should avoid assuming universal Five9 event coverage and can use scheduled retrieval when push notifications are unavailable. |
How to build a Five9 integration in Martini
Objective
Establish the Five9 connection using the API style and permissions required by the use case. Keep tenant, domain, endpoint, WSDL version, credentials, tokens, and scopes outside workflow logic.
Instructions in Martini
- Confirm whether the required Five9 capability is exposed through REST or SOAP
- Create a least-privilege Five9 integration identity
- Store credentials and tokens in Martini-managed environment secrets
- Configure the Five9 domain, endpoint, API version, and authentication settings
Objective
Select a trigger that matches the availability and reliability of the Five9 capability. Do not assume that a universal Five9 webhook is available.
Instructions in Martini
- Use a supported notification or callback only after confirming product-specific coverage
- Use a scheduler for polling, reporting extraction, or incremental synchronization
- Define the event, timestamp, status, or cursor used to identify changes
- Set an execution window and controlled concurrency for high-volume work
Objective
Retrieve the current Five9 object or reporting result and account for incomplete notifications, pagination, asynchronous jobs, and tenant-specific API behavior.
Instructions in Martini
- Call the documented REST resource or SOAP operation
- Poll supported report or batch jobs with bounded retries and timeouts
- Process pages, cursors, date windows, or result sets according to the selected API
- Persist checkpoints so interrupted runs can resume safely
Objective
Coordinate retrieval, validation, enrichment, business rules, target writes, and operational outcomes in a maintainable Martini workflow.
Instructions in Martini
- Separate Five9 transport calls from transformation and target-system logic
- Resolve related Agents, Contacts, Campaigns, Queues, or Dispositions where needed
- Route records conditionally based on disposition, lifecycle, status, or business priority
- Use reusable services or workflow components for shared integration logic
Objective
Convert Five9 XML or JSON payloads into a canonical model and then into the target system's contract without losing source identifiers or business meaning.
Instructions in Martini
- Map stable Five9 identifiers into the canonical model
- Normalize timestamps, time zones, phone numbers, and status values
- Maintain explicit mappings for Dispositions and target statuses
- Validate required fields before writing downstream
Objective
Enforce data ownership, privacy, authorization, duplicate prevention, and routing policies before changing Five9 or downstream systems.
Instructions in Martini
- Define which system owns each synchronized attribute
- Minimize personal and payment-related data in payloads and logs
- Use stable identifiers and source-to-target maps for idempotency
- Reject or quarantine records that fail validation or authorization rules
Common Five9 data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Agents | Represent contact-center users who handle customer interactions and may be associated with provisioning, skills, queues, or performance reporting. | Workday, identity-management systems, Salesforce, ServiceNow, Snowflake | Martini can retrieve or provision Agents through the applicable administrative API, validate lifecycle changes, map identifiers and attributes, and record results for reconciliation. |
| Campaigns | Organize inbound, outbound, or blended contact-center activity and related operational configuration. | Salesforce, Microsoft Dynamics 365, Snowflake, ServiceNow | Martini can map campaign attributes, enforce configuration rules, sequence dependent updates, and synchronize campaign-related data through documented REST or SOAP operations. |
| Contacts | Store customer or prospect information used in dialing, campaigns, and interaction workflows. | Salesforce, Microsoft Dynamics 365, Zendesk, NetSuite | Martini can synchronize Contacts using stable identifiers, validation, duplicate detection, field ownership rules, incremental retrieval, and explicit retry behavior. |
| Dispositions | Capture outcome codes assigned after completed interactions and support follow-up or reporting processes. | Salesforce, ServiceNow, Zendesk, Snowflake | Martini can normalize Five9 Dispositions into target-specific statuses, apply business rules, and prevent ambiguous outcome labels from being copied without an explicit mapping. |
| Skills | Describe agent capabilities used for routing and workforce assignment. | Workday, identity-management systems, ServiceNow, Snowflake | Martini can validate and sequence Skill updates with Agent and other dependent configuration changes, while recording authorization and validation failures separately. |
| Queues | Define routing destinations used to organize and distribute interactions. | Five9 administration stores, reporting warehouses, ServiceNow | Martini can extract or update Queues where the selected API and permissions support those operations, using controlled concurrency, dependency checks, and reconciliation. |
Authentication and security considerations
Authentication and least privilege
Five9 access is authenticated and permission-controlled. SOAP Web Services API credentials and REST authentication, including any OAuth 2.0 flow, should be configured according to the selected API and should not be treated as interchangeable.
- Use a dedicated Five9 integration identity with only the required permissions.
- Store credentials, tokens, domains, endpoints, scopes, and WSDL settings in Martini-managed environment secrets.
- Separate development, test, and production configuration.
- Minimize personal and payment-related data in workflow payloads and logs.
- Restrict access to administrative operations affecting Agents, Campaigns, Skills, Queues, Contacts, and reporting data.
Operational considerations for Five9 integrations
Design for tenant-specific behavior
Five9 behavior can vary by domain, tenant, product package, geographic deployment, enabled modules, API version, and permissions. Confirm the selected endpoint and object coverage before implementation.
- Use controlled concurrency, backoff, and retry policies for rate or service limits.
- Support pagination, cursors, date windows, or asynchronous jobs where the selected API requires them.
- Persist checkpoints and source identifiers to support incremental recovery and idempotency.
- Treat WSDL changes, namespaces, enumerations, and response schemas as controlled changes requiring regression testing.
- Distinguish authentication, authorization, validation, throttling, transient service, and downstream failures.
- Normalize time zones and account for late-arriving updates during extraction windows.
- Use explicit mappings for Dispositions rather than inferring business meaning from labels.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration beyond point-to-point calls
Martini provides a maintainable integration layer between Five9 and the rest of the enterprise. It can combine SOAP and REST calls, scheduled retrieval, target-system APIs, validation, transformation, and business rules in governed workflows.
- Centralize Five9 authentication and environment-specific configuration.
- Reuse mappings, validation logic, identifier resolution, and error-handling patterns.
- Coordinate multi-step processes such as provisioning Agents, Skills, and Queues.
- Support incremental synchronization, checkpoints, retries, and exception routing.
- Expose controlled APIs without coupling internal applications directly to Five9.
- Provide workflow logs and operational visibility across the complete integration rather than only one API call.
Frequently asked questions
Five9 can be integrated through its documented SOAP Web Services API, selected REST APIs, reporting or export capabilities, and product-specific notification mechanisms when available. Where push events are not confirmed, scheduled polling and incremental retrieval can support synchronization. Authentication, object coverage, permissions, and limits should be confirmed for the relevant Five9 tenant and product.
Yes. Martini can consume Five9 REST APIs where the required capability is available, consume the Five9 SOAP Web Services API, orchestrate reporting or export workflows, transform XML and JSON payloads, and synchronize Five9 data with enterprise applications. A universal Five9 webhook capability should not be assumed.
No. A dedicated Five9 connector is not required. Martini can integrate with Five9 using the vendor's confirmed native REST APIs, SOAP Web Services API, reporting or export mechanisms, and product-specific notifications or callbacks where those are documented.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Five9 with Martini. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Five9, cloud infrastructure, or other third-party systems depending on subscriptions, usage, and deployment model.
Use REST for the documented Five9 resources that expose the required capability. The SOAP Web Services API may be required for administrative, configuration, reporting, or contact-center operations not available through the relevant REST API. Confirm object and operation coverage, authentication, and tenant permissions before selecting the design.
A universal Five9 webhook mechanism covering all contact-center events was not confirmed. Some products may provide notifications, callbacks, streaming, or integration-specific mechanisms, but coverage must be verified for the selected service. Martini can receive a confirmed notification or use scheduled polling and incremental retrieval when push delivery is unavailable.
Reliable synchronization should use stable Five9 identifiers, explicit field ownership, incremental timestamps or vendor-supported cursors, and mappings for objects such as Contacts, Agents, Campaigns, and Dispositions. Martini can validate, transform, deduplicate, checkpoint, retry transient failures, and reconcile results across systems.
Yes. Martini can expose controlled REST APIs for internal applications or external systems and use workflows behind those APIs to call Five9 REST or SOAP services. This can centralize authentication, validation, business rules, data transformation, and error handling without exposing Five9 credentials or implementation details directly.
Related Martini documentation
Five9 APIs
Data Processing
Security and Operations
Integrate Five9 with Martini
Use Martini to connect Five9 APIs and contact-center data with enterprise applications through secure, observable workflows and reusable integration services.