From Custom Scripts to Native Connectors: A360.41 Expands the Automation Surface

Every automation developer knows the drill. You need your automation to talk to Slack, or pull a file from Box, or kick off a Databricks job. But before you write a single line of business logic, you're building an integration that can handle OAuth, manage tokens, writing error handling for an API you didn't design and don't control. Multiply that across a dozen more enterprise systems and their automations, you will soon realize that integration work quietly becomes the biggest line item in your automation backlog.

The challenge isn't building automation logic. It's connecting automation to the systems where work actually happens. A360.41 allows teams to automate more processes across more systems with less custom development effort.
 

What's new in A360.41

A360.41 introduces 12 native connectors across five categories that reflect how modern enterprises operate, spanning content management, collaboration, identity, analytics, and software delivery ecosystems.

Every connector in this release follows the same design pattern:

• OAuth2 or personal-access-token (PAT) authentication
• Pre-built actions designed for real jobs (not thin API wrappers)
• Iterators for bulk operations

All of this is available without custom scripting. Each is supported for both Task Bots and API Tasks, and each runs on Windows and macOS.

That consistency matters as much as the connector count. A developer who's built one of these integrations already knows the shape of the next one: connect, act, iterate, disconnect. Less time relearning a new pattern for every system means more time on the automation logic that actually matters to the business.

Here's a closer look at each connector, what it plugs into, and where it earns its place in your automation stack.

Box: Content automation without shuffling files manually

Connects to: Box

The Box connector gives automation full lifecycle control over files and folders — upload, download, copy, move, delete, and search files; create, delete, list, and search folders; and generate shared links, all authenticated through Control Room-managed OAuth2.

If your team is still manually filing invoices into Box folders or hunting down documents for a case file, this is the connector that ends that hunt. It's built for the enterprise use cases - invoice handling, case management, content routing - where content has to move reliably and leave an audit trail.

Check out the new course on using Box connector here.

PowerPoint: Turn data into decks automatically

Connects to: the desktop Microsoft PowerPoint app

The PowerPoint connector automates the presentation workflows that eat up hours every reporting cycle: create, open, and save presentations; add, update, copy, or delete slides; insert text, tables, and pictures; and format or replace text and images directly in the deck.

This is the connector for anyone who's ever manually refreshed the same 40-slide deck with new numbers every month. Generate decks straight from business data, keep recurring reports current, refresh branded templates, and export the finished product, all from an automation instead of a copy-paste marathon.

Slack: Automate the conversations, not just the tasks

Connects to: Slack

The Slack connector lets automation retrieve workspace, channel, and user details, send messages person-to-person or into a channel, and iterate through channels, messages, conversations, or users, all through Control Room-managed OAuth2 authentication.

Slack is where a lot of operational work actually happens: approvals, incident routing, status pings and, until now, most of that remained a manual process. With this connector, an automation can notify the right stakeholders the moment something needs attention, route an incident to the right channel, capture an approval reply, or mine conversation history for follow-ups.

Check out the new course on using Slack connector here.

Gmail: Automate the mailbox

Connects to: a Gmail mailbox

The Gmail connector covers the full email lifecycle an automation needs: send or forward messages, reply or reply-all, move or delete emails individually or in bulk, save emails and their attachments, retrieve emails based on filter conditions, and check whether a label exists, authenticated via Control Room-managed OAuth2.

Anyone who's built an email-triggered process knows how much of that logic is just plumbing: watching for the right message, pulling the attachment, filing it, replying. This connector handles that plumbing natively, so the automation logic can focus on what happens with the email content, not on wrestling with the mailbox.
 

Asana: Keep project work and automation in sync

Connects to: Asana

The Asana connector brings project and task management into your automation workflows. Connect to a workspace, create, retrieve, update, and delete projects and tasks, and create, retrieve, update, and delete comments on a task.

The value here is straightforward: work status shouldn't live in two disconnected places. When a task changes state in Asana, an automated workflow can react by updating a downstream system, notifying a channel, or kicking off the next step without someone manually bridging the two systems.
 

Jira: Automate issue-driven workflows

Connects to: Jira

The Jira connector syncs work, automates transitions, and triggers actions based on issue state changes, letting teams route issue-based work into broader automation pipelines instead of tracking it by hand.

For any team running incident response, bug triage, or change management through Jira, this connector removes the manual handoff between "the ticket changed" and "something happens because of it."
 

Okta: Identity workflows without the ticket queue

Connects to: Okta

The Okta connector covers the identity lifecycle end to end: create, update, delete, activate, and deactivate users; add or remove users from groups; search groups and users; and retrieve group or user details, all through Control Room-managed OAuth2 authentication.

On-boarding, off-boarding, and access cleanup are exactly the kind of high-volume, rules-based work that shouldn't require a human clicking through an admin console one account at a time. This connector lets IT automate those workflows end to end, cutting ticket volume and shrinking the gap between "someone joined the team" and "someone can actually log in."
 

Databricks: Bring data processing into the workflow

Connects to: Databricks

The Databricks connector lets automation run SQL statements or jobs and retrieve their results or status, cancel a running SQL statement or job, and upload, download, or delete files, all authenticated via Control Room-managed OAuth2 or a personal access token.

This connector lets you do things like automate an hours-long invoice reconciliation process: receive the file, run validation and matching across systems, review accepted and rejected invoices, and manually prepare and share a reconciliation report. With the Databricks connector in place, that becomes: upload an invoice file to Unity Catalog Volume, run the reconciliation job, and retrieve the summary of the report via SQL queries automatically. You can now get real-time visibility in minutes not hours to reconcile your daily invoices across different vendors.
 

Kafka: Stream events straight into your automations

Connects to: Kafka

The Kafka connector brings real-time event streaming into automation workflows, with actions to connect, publish a message, consume a message, and commit offsets.

Most automation triggers today are either scheduled or manually kicked off. Kafka changes that: an automation can react the moment an event lands on a topic, instead of waiting for the next poll cycle. That's the difference between "we'll catch it on the next run" and "we caught it as it happened."
 

Snowflake: Query analytics into your decision logic

Connects to: Snowflake

The Snowflake connector lets automations query analytics data to power decisions and actions, bringing live data into the logic an API Task uses to decide what happens next.

Instead of exporting a report and acting on stale numbers, an automation can query Snowflake directly and make a decision based on what's true right now.
 

Azure DevOps: Run your CI/CD pipelines from an automation

Connects to: Azure DevOps

The Azure DevOps connector automates core continuous integration/continuous delivery (CI/CD) operations: create, update, delete, and run pipelines based on YAML configuration; retrieve pipeline and execution details; and pass runtime parameters, variables, and skipped stages to simplify a pipeline run, all authenticated with a personal access token.

For engineering teams already running CI/CD, this connector means pipeline operations can become one more step in a broader automated workflow, not a separate system that has to be triggered by hand.
 

GitHub: Automate the collaboration layer of engineering

Connects to: GitHub

The GitHub connector automates the day-to-day mechanics of collaborative development: create, update, or retrieve issues; create, merge, or retrieve pull requests and add comments; and retrieve repository and branch details, authenticated with an API key.

Whether it's auto-filing issues from an error log, keeping pull request status in sync with a project tracker, or routing repository activity into a broader business process, this connector lets GitHub activity plug into the same automation fabric as everything else your bots touch.

The Bigger Picture

These twelve native connectors help organizations automate across the business landscape through governed, reusable integrations, reducing custom development effort while accelerating delivery, simplifying maintenance, and expanding automation coverage across the enterprise.

Business Outcomes:

• Faster automation development
• Reduced integration effort
• Improved governance
• Lower maintenance costs
• Broader automation coverage

Try it yourself

Twelve native connectors, one consistent pattern, five categories of enterprise systems that lets you free from custom integration work and maintenance overhead, allowing you to focus on what matters: the automation logic.

If you're ready to see it in your own environment, "Try the new connectors in Automation 360", or dig into the specifics in the product documentation for each connector.