Ellipse Gradient for Header

Automation Anywhere Integration Guide

Connect Automation Anywhere Control Room with enterprise systems through REST APIs, selected event notifications, asynchronous execution, queues, and secure workflow orchestration.

Automation Anywhere integration options at a glance

Automation Anywhere Automation 360 primarily integrates through Control Room REST APIs for authentication, bot management, execution, devices, users, roles, queues, work items, audit information, and supported package operations. Selected Automation 360 scenarios provide event or webhook-style notifications, but coverage varies by release and object, so scheduled polling remains important. Asynchronous bot execution and queue processing can be coordinated using execution and work-item identifiers. Martini can securely call these APIs, transform JSON payloads, expose a controlled API for enterprise callers, persist synchronization state, and orchestrate polling, validation, retries, and downstream updates without relying on direct access to the Control Room database.

Integration pointSupported by Automation Anywhere?Common use casesHow Martini supports it
REST APIsYesControl Room REST APIs support authentication, bot management, execution, devices, users, roles, queues, work items, audit information, and other platform operations. Exact paths and fields vary by release.Martini can consume authenticated REST APIs, map JSON requests and responses, apply business rules, persist state, and expose reusable API-led workflows.
AuthenticationYesControl Room uses authenticated and permission-controlled API access. Token, OAuth 2.0, bearer-token, API-key, and role requirements depend on the edition and API version.Martini stores credentials in secrets or environment configuration and uses them in secured API workflows without embedding them in payloads or logs.
Webhooks / outbound callbacksLimitedAutomation 360 provides event-driven or webhook-style capabilities for selected scenarios, but not every bot state, queue change, audit event, or Control Room object produces a notification.Martini can receive supported webhook notifications and use scheduled polling when the required event is unavailable.
Bulk / async / batch APIsLimitedAsynchronous bot execution and queue or work-item processing are supported. Bulk behavior is endpoint-specific and should be confirmed for high-volume operations.Martini can submit work, store execution or work-item identifiers, poll status, limit concurrency, and reconcile results.
File / attachment APIsLimitedSupported Control Room operations may upload, download, promote, or manage bot packages and related automation assets, often using multipart requests.Martini can orchestrate package transfers, map metadata, separate long-running transfer stages, and record deployment outcomes.
Scheduled synchronizationYesScheduled API polling can synchronize bots, devices, users, queues, audit information, and execution history when event coverage is unavailable.Martini scheduler-triggered workflows can paginate through results, maintain watermarks, and apply idempotent updates to target systems.
Database accessNoDirect access to the internal Control Room database is not a standard or recommended integration method.Martini should use supported Control Room APIs or a separately documented analytics interface rather than querying internal tables.

How Automation Anywhere exposes data and business events

Automation Anywhere REST APIs

Automation Anywhere Control Room exposes REST APIs for authentication, bot management, execution, devices, users, roles, queues, work items, audit information, and selected package operations. API paths, fields, and permissions depend on the Automation 360 or Enterprise release and deployment model.

Martini implementation pattern

Martini uses a workflow to authenticate against Control Room, call the required REST resources, transform Automation Anywhere JSON into a canonical model, and invoke downstream applications or persistence services. A Martini API can provide a stable enterprise-facing façade while keeping Control Room-specific paths and credentials inside the integration layer.

Implementation sequence

Store the Control Room base URL and credentials in Martini secrets
Authenticate against the target Control Room API
Call the required REST resource with authorized parameters
Paginate through responses when the endpoint is paginated
Map Automation Anywhere JSON to the canonical model
Apply validation, routing, and authorization rules

Automation Anywhere Webhooks and Events

Automation 360 supports event-driven or webhook-style capabilities for selected scenarios, but notification coverage is not universal across bots, queues, audit events, or other Control Room objects. The relevant event must be verified for the target release.

Martini implementation pattern

Martini can receive a supported notification, validate its signature or authentication requirements where applicable, and retrieve the current Control Room resource before processing it. When the required event is unavailable, a scheduler-triggered Martini workflow polls the relevant API using a watermark or execution identifier.

Implementation sequence

Confirm that the required event is supported in the target release
Receive the notification through a secured Martini endpoint when available
Validate the event and extract the execution or object identifier
Retrieve the current Control Room state
Apply idempotency and business-state checks
Write the result to the target system and record the checkpoint

Automation Anywhere Async Execution and Queues

Automation Anywhere supports asynchronous bot execution and work-queue-oriented processing. Starting a bot or submitting a work item can return an execution or work-item identifier that must be tracked until the business process reaches an acceptable state.

Martini implementation pattern

Martini accepts or retrieves source transactions, validates them, and submits eligible work to Control Room. It stores the business correlation ID, execution ID, work-item ID, and timestamps, then polls status or handles a supported notification. Retry logic checks for an active original item before resubmitting.

Implementation sequence

Receive the source transaction or scheduled work set
Validate required business fields and the correlation ID
Submit the work item or start the authorized bot
Store the returned execution or work-item identifier
Poll status or process a supported completion notification
Reconcile the final result and prevent duplicate submission

Automation Anywhere File and Package APIs

Supported Control Room operations may upload, download, promote, or manage bot packages and related automation assets. These operations can use multipart requests, distinct permissions, and version-specific package endpoints.

Martini implementation pattern

Martini separates package transfer from deployment orchestration, stores package metadata and checksums where supported, and invokes the appropriate Control Room operation. The workflow validates the target environment and records deployment or transfer status for release and audit processes.

Implementation sequence

Retrieve the approved package and deployment metadata
Validate the target environment and integration permissions
Upload or download the package using the supported operation
Verify the response, package identifier, or checksum where available
Coordinate deployment or promotion through Control Room
Record the outcome and route failures for review

Common Automation Anywhere integration patterns

Pattern 1: Submit business work to an Automation Anywhere queue

When to use this pattern

Use this pattern when Salesforce, SAP S/4HANA, NetSuite, ServiceNow, or another source application needs to submit transactions for unattended or attended processing. It separates intake from execution and supports controlled retries and reconciliation.

Integration direction
Source application
Martini
Automation Anywhere
Example Mapping
Automation Anywhere FieldCanonical FieldTarget Field
sourceTransactionIdbusinessCorrelationIdworkItem.reference
customerOrAccountIdpartyIdworkItem.businessData.partyId
requestedOperationautomationTypequeue.name
submittedAtsubmittedTimestampworkItem.metadata.submittedAt
Martini implementation pattern

A Martini API or scheduled workflow validates the source transaction, checks for an existing active correlation ID, maps the payload to the target queue format, and submits the work item through the Control Room REST API. A follow-up workflow polls status, applies completion and exception rules, and updates the source system. Transient failures are retried with backoff; duplicate submissions are blocked using the correlation record.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • scheduled execution
  • error handling

Pattern 2: Trigger and monitor a bot from an enterprise API

When to use this pattern

Use this pattern when an enterprise application needs a controlled endpoint to request a bot run without exposing Control Room directly. It is appropriate for approved operations that require authorization, validation, and asynchronous status tracking.

Integration direction
Enterprise application
Martini
Automation Anywhere
Example Mapping
Automation Anywhere FieldCanonical FieldTarget Field
botNameautomationIdentifierbot.id
requestedByrequesterIdexecution.requestedBy
inputPayloadautomationInputexecution.parameters
executionIdexternalExecutionIdstatus.executionId
Martini implementation pattern

Martini exposes a secured REST API, validates the caller and request, resolves the permitted bot, and calls Control Room to start it. The workflow returns an accepted response with a correlation and execution identifier, then polls execution status or processes a supported event. It maps terminal states to a stable enterprise status and creates an operational exception when the bot succeeds but downstream validation fails.

Martini capabilities used
  • API exposure
  • authentication and authorization
  • API consumption
  • data mapping
  • asynchronous workflows
  • monitoring

Pattern 3: Synchronize bot inventory and operational metadata

When to use this pattern

Use this pattern when an organization needs a normalized view of bots, devices, bot runners, users, roles, audit logs, or execution history in a database, CMDB, or service-management platform.

Integration direction
Automation Anywhere
Martini
ServiceNow
Example Mapping
Automation Anywhere FieldCanonical FieldTarget Field
bot.idautomationIdconfigurationItem.externalId
device.nameruntimeNameconfigurationItem.name
execution.statusexecutionStateautomationRun.status
audit.createdAteventTimestampauditEvent.occurredAt
Martini implementation pattern

A scheduler-triggered Martini workflow calls the applicable Control Room list endpoints, follows pagination, and uses last-seen timestamps or object identifiers as watermarks. It normalizes version-specific status values, upserts target objects, and preserves unknown fields where appropriate. Rate limits are respected through bounded concurrency and backoff, while failed pages are retried without replaying completed updates.

Martini capabilities used
  • scheduler triggers
  • API consumption
  • pagination handling
  • mapping and transformation
  • state persistence
  • retry handling

Pattern 4: Coordinate bot deployment with release management

When to use this pattern

Use this pattern when approved bot packages must be promoted between environments and the deployment result must be recorded in an enterprise release or audit system.

Integration direction
Release management platform
Martini
Automation Anywhere
Example Mapping
Automation Anywhere FieldCanonical FieldTarget Field
release.iddeploymentIdpackage.metadata.releaseId
package.fileautomationArtifactbotPackage.content
targetEnvironmentdeploymentEnvironmentcontrolRoom.environment
deploymentResultdeploymentStatusrelease.status
Martini implementation pattern

Martini receives an approved release request, validates package metadata and target permissions, and performs the supported upload, download, or promotion operation. It records package identifiers, response details, and deployment status, then updates the release system. Multipart failures, package-size problems, and permission errors are isolated and routed for remediation rather than retried indefinitely.

Martini capabilities used
  • workflows
  • file handling
  • API consumption
  • validation
  • business rules
  • error handling

Applications commonly integrated with Automation Anywhere

Automation Anywhere can be integrated with named enterprise applications when a process combines API-based data exchange with attended or unattended automation. Martini can provide the orchestration, transformation, correlation, and error handling layer between these systems and Control Room.

Application Scenario Direction Martini Pattern
Salesforce Automate customer, lead, case, or service processes that require interaction with systems beyond Salesforce APIs. Salesforce → Martini → Automation Anywhere Martini receives a Salesforce request or scheduled change, validates and maps it to a Control Room bot or queue work item, stores the correlation identifier, and synchronizes execution results back to Salesforce.
ServiceNow Submit incidents, requests, or operational work to bots and return processing status, evidence, or exception details. ServiceNow → Martini → Automation Anywhere A Martini workflow consumes ServiceNow data, applies routing rules, submits a work item or starts an authorized bot, polls completion when necessary, and updates the originating ServiceNow record.
SAP S/4HANA Coordinate transactions or legacy processes where direct application integration does not cover the complete business process. SAP S/4HANA → Martini → Automation Anywhere Martini normalizes SAP input, invokes the appropriate Automation Anywhere process, tracks the execution identifier, and returns validated results or exceptions to SAP or an operational data store.
Workday Coordinate employee, payroll, or finance-related processes involving applications that require unattended or attended automation. Workday → Martini → Automation Anywhere Martini receives an approved Workday event or scheduled dataset, applies business rules and sensitive-data handling, submits eligible work to Control Room, and records status for downstream reconciliation.
Jira Create or update issues when bot execution fails, needs human review, or completes a controlled deployment process. Automation Anywhere → Martini → Jira Martini evaluates execution and audit results, applies severity and ownership rules, and creates or updates Jira issues with redacted diagnostic context and correlation identifiers.
Microsoft SharePoint Process documents, approvals, and files through bots while returning status or output documents to SharePoint. Microsoft SharePoint → Martini → Automation Anywhere Martini retrieves approved SharePoint metadata or files, coordinates a package or bot operation in Control Room, and writes the resulting status or artifact reference back to SharePoint.
NetSuite Automate finance and order-processing tasks where a combination of APIs and UI automation is required. NetSuite → Martini → Automation Anywhere Martini transforms NetSuite transactions into queue work items or bot inputs, enforces duplicate and approval rules, and reconciles completion results against the source transaction.
Zendesk Automate support-ticket enrichment, updates, or back-office processing and return results to support agents. Zendesk → Martini → Automation Anywhere Martini routes eligible Zendesk tickets to a bot or queue, tracks asynchronous processing, and updates the ticket with a controlled result, exception, or review status.

How to build a Automation Anywhere integration in Martini

Objective

Establish a version-aware connection to the target Automation Anywhere Control Room without exposing credentials in workflows or payloads.

Instructions in Martini

  • Confirm the Automation Anywhere edition, deployment model, API version, base URL, tenant, and required permissions.
  • Store tokens, API credentials, or OAuth configuration in Martini secrets or secured environment configuration.
  • Use the Control Room authentication method required by the target release.

Objective

Select the event, API request, or schedule that starts the integration based on the confirmed Automation Anywhere capabilities.

Instructions in Martini

  • Use a Martini API when an enterprise application needs to request a bot or queue operation.
  • Receive a supported Automation Anywhere notification only for verified event coverage.
  • Use a scheduler-triggered workflow for polling, inventory synchronization, or unsupported event scenarios.

Objective

Receive or retrieve the current Automation Anywhere resource and preserve the identifiers required for asynchronous processing.

Instructions in Martini

  • Call the relevant Control Room REST resource with authorized parameters.
  • Follow pagination for bots, devices, users, queues, audit logs, or execution history.
  • Store execution IDs, work-item IDs, device IDs, timestamps, and business correlation IDs.

Objective

Coordinate Control Room calls, source systems, target systems, and asynchronous status checks in a maintainable Martini workflow.

Instructions in Martini

  • Separate intake, submission, status polling, reconciliation, and notification stages where appropriate.
  • Use bounded concurrency and scheduled polling intervals instead of tight loops.
  • Persist checkpoints and processing state so a workflow can resume safely.

Objective

Convert Automation Anywhere JSON and status structures into the canonical model required by connected applications.

Instructions in Martini

  • Map bot, queue, work-item, device, user, execution, and audit fields explicitly.
  • Validate required identifiers, status values, permissions, and business data before submission.
  • Preserve or log unknown fields safely when version-specific responses evolve.

Objective

Control which work is submitted, retried, escalated, or reconciled based on business and operational conditions.

Instructions in Martini

  • Check for an active correlation ID before retrying a submission.
  • Distinguish bot completion from successful completion of the downstream business process.
  • Route permission failures, invalid data, and terminal automation errors to appropriate operational handling.

Common Automation Anywhere data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
BotsList, retrieve, manage, start, or monitor task bots and other automations in Control Room.ServiceNow, Salesforce, Jira, release-management platforms, operational databasesMartini retrieves bot metadata or invokes supported bot operations, normalizes version-specific fields, stores identifiers, and applies authorization and routing rules.
Bot runnersRepresent execution resources assigned to run automations.Operational databases, service-management platforms, monitoring systemsMartini synchronizes runner availability and identifiers, correlates them with execution status, and avoids assuming that a completed bot means the business process is complete.
DevicesRepresent workstations or runtime environments registered with Control Room.CMDBs, ServiceNow, asset databases, monitoring systemsMartini paginates device data, maps environment and status fields, and reconciles changes using stable identifiers and watermarks.
Users and rolesRepresent Control Room identities, permissions, and tenant access.Identity governance platforms, audit stores, ServiceNowMartini synchronizes only authorized fields, preserves role relationships, and applies least-privilege handling for sensitive administrative data.
Work items and queuesSubmit and process transactional work for unattended or attended automation.Salesforce, SAP S/4HANA, NetSuite, ServiceNow, operational databasesMartini validates source transactions, submits queue items where supported, stores business correlation IDs, and polls or processes completion status idempotently.
Audit logsRecord operational and administrative activity for monitoring, compliance, and investigation.Jira, ServiceNow, SIEM or audit databasesMartini retrieves available audit information, redacts sensitive values, maps event types, and stores correlation and timing data for operational reporting.

Authentication and security considerations

Version-aware authentication

Automation Anywhere authentication varies by deployment model, product edition, and API generation. Confirm whether the target Control Room requires OAuth 2.0, bearer tokens, API credentials, or another token-based flow before implementation.

Least-privilege access

Use a dedicated integration identity with only the permissions required to view, submit, run, deploy, or administer the relevant objects. Control Room roles may distinguish these activities.

Secret protection

  • Store base URLs, tokens, API keys, and client credentials in Martini secrets or secured environment configuration.
  • Do not place credentials, Credential Vault references, or sensitive automation inputs in workflow payloads or logs.
  • Redact response bodies and package metadata where they may contain protected business information.

Operational considerations for Automation Anywhere integrations

Rate limits and pagination

Confirm tenant-specific rate limits, concurrency constraints, and list-response pagination. Use bounded concurrency, response-aware handling for throttling, and backoff rather than tight polling loops.

Asynchronous execution

Store execution IDs, work-item IDs, bot and device identifiers, timestamps, status, and error details. A successful bot run may not mean that the downstream business process has completed successfully.

Idempotency and retries

Maintain a Martini-side correlation record and check whether an original execution or work item remains active before retrying. Use watermarks or last-seen timestamps for synchronization and avoid replaying completed pages.

Version and schema changes

Automation Anywhere API paths, status values, permissions, and response structures can vary between releases. Test against the target Control Room version and handle unknown fields and status changes conservatively.

Files and observability

Package operations may use multipart requests, size limits, distinct permissions, and longer processing times. Capture correlation IDs, HTTP status, timing, and redacted response details for troubleshooting.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration beyond a script

Martini coordinates intake, Control Room calls, asynchronous status checks, downstream updates, and operational notifications in workflows rather than concentrating all logic in a one-off script.

Reusable API-led integration

Martini can expose a controlled API façade so enterprise applications do not need to understand Automation Anywhere-specific endpoints, credentials, or version differences.

Reliable transformation and control

Mappings, validation, business rules, checkpoints, retries, and error handling can be managed as reusable integration assets. This supports queue submissions, inventory synchronization, package deployment, and result reconciliation across multiple systems.

Maintainable operations

Centralized secrets, logging, correlation identifiers, and workflow monitoring make it easier to troubleshoot and evolve integrations as Control Room versions, permissions, and payload structures change.

Frequently asked questions

How can Automation Anywhere be integrated with enterprise systems?

Automation Anywhere Automation 360 can integrate through Control Room REST APIs for authentication, bot management, execution, devices, users, roles, queues, work items, audit information, and selected package operations. Selected scenarios also support event or webhook-style notifications, while scheduled API polling can cover events that are not exposed.

Can Martini integrate with Automation Anywhere?

Yes. Martini can consume Automation Anywhere Control Room REST APIs, receive supported event or webhook notifications, orchestrate asynchronous bot and queue processing, transform JSON payloads, and expose a secured API for enterprise applications that need to invoke or monitor Automation Anywhere operations.

Do I need a connector to integrate Automation Anywhere with Martini?

No dedicated Automation Anywhere connector is required. Martini can integrate using Automation Anywhere's confirmed native mechanisms, primarily Control Room REST APIs, supported authentication methods, selected notifications, asynchronous execution, queues, and supported file or package operations.

Is there any extra Lonti cost to integrate Automation Anywhere with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Automation Anywhere. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Automation Anywhere, cloud infrastructure, or other third-party systems depending on subscription, usage, and deployment model.

Which Automation Anywhere integration methods should be used?

REST APIs are the primary integration surface for new Automation Anywhere integrations. Use asynchronous execution and queue or work-item APIs where supported, selected event notifications when confirmed for the target release, and scheduled polling when notifications are unavailable. Direct database access should not be used as the standard approach.

Does Automation Anywhere provide webhooks or events for bot activity?

Automation Anywhere provides event-driven or webhook-style capabilities for selected Automation 360 scenarios, but coverage is not universal across bots, queues, audit events, or other Control Room objects. The relevant event must be verified for the deployed release; otherwise, Martini can poll supported APIs on a schedule.

How does synchronization with Automation Anywhere work?

Martini can synchronize Automation Anywhere objects by calling paginated Control Room APIs, mapping them to a canonical model, and writing them to applications or databases. Watermarks, timestamps, stable identifiers, execution IDs, and business correlation IDs help maintain incremental and idempotent synchronization.

How are Automation Anywhere data mapping, errors, retries, and duplicates handled?

Martini maps Automation Anywhere JSON into target-specific models, validates business rules, and records correlation and execution identifiers. Workflows can retry transient failures with backoff, respect throttling, route terminal errors for review, and check whether an original execution or work item is active before submitting a duplicate.

Can Martini expose an API façade for Automation Anywhere?

Yes. Martini can expose a secured REST API that validates callers and requests, invokes authorized Control Room operations, hides version-specific vendor details, and returns or persists a stable correlation and execution status model. GraphQL was not confirmed as an Automation Anywhere API, and no current SOAP surface was verified.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Connect Automation Anywhere with your enterprise systems

Use Martini to orchestrate Automation Anywhere Control Room APIs, queues, asynchronous executions, selected notifications, and downstream business processes through maintainable workflows and secured APIs.

EXPLORE MARTINI
BOOK A DEMO