InvGate Service Management includes a no-code workflow builder that helps teams automate processes such as onboarding, access requests, and offboarding.
Built-in Action Connectors extend those workflows beyond the platform, allowing them to retrieve information from external tools or trigger actions in them instead of stopping when another system is involved. You can keep processes moving across the tools your teams already use, reducing manual steps and keeping related actions connected.
In this article, we’ll look at how Built-in Action Connectors work, what they can automate, and where they can help you build more complete workflows.
What are the Built-in Action Connectors in InvGate?
Built-in Action Connectors are pre-configured actions for third-party tools that live directly inside InvGate’s no-code workflow builder.
Each connector represents something concrete that a workflow can do in another system, like creating a user, adding them to a group, or scheduling a meeting. Rather than configuring web services from scratch, workflow designers drag these actions into the workflow and fill in a few parameters using simple form fields.
What’s left is defining when the action should run and what information it needs. And all of this happens using the same visual builder teams already rely on, without custom development or technical setup becoming a barrier.
InvGate Service Management gives teams a visual way to design workflows, route requests, and apply automation rules. Built-in Action Connectors build on that foundation and turn workflows into something closer to an execution layer, not just a coordination map.
Workflows move from “hand off the work” to “do the work,” without adding technical complexity for the people designing them.
How do Built-in Action Connectors work?
Service requests rarely belong to a single system. Onboarding alone touches identity platforms, collaboration tools, calendars, and communication channels. The same holds for offboarding, access requests, maintenance announcements, and internal changes, which all cross tool boundaries.
In a traditional workflow builder, teams have two options:
- Handle those steps manually outside the workflow.
- Rely on custom web services that require technical knowledge to set up.
Built-in Action Connectors remove that tradeoff. They are ready-to-use steps inside the InvGate Service Management workflow editor that link a process to external applications and services, with no integration built from scratch. Each connector either reads live data from a connected system or performs an action in it, and that step lives in the same place as approvals, conditions, and routing.
Because the actions come preconfigured, three things follow:
- Fast implementation. The action is ready to use once dropped in, with no integration coded from the ground up.
- Fewer runtime errors. A connector requires its credentials to be set before it can run, which prevents failures from missing data.
- Credential reuse. Credentials configured once carry across stages and workflows, so multi-step processes stay consistent.
Connectors appear in the Steps Menu of the workflow editor. To add one, drag it into the diagram. If no credentials exist yet, a setup form opens for the required fields; once saved, the connector is live. If credentials already exist, select the one to use and enable "Reuse credential" so the same connection carries across every action in the workflow.
Available connectors
InvGate Service Management connects to the systems teams already run on, across identity, HR, collaboration, calendars, documents, project management, CRM, and IT operations. Each connector becomes a step you build into a workflow, reading live data from a system or carrying out an action in it, so a process can move across tools the same way it moves through approvals and routing.
Identity and access management
- Okta — list users and groups, and a user's group and application memberships.
- Entra ID — create, enable, disable, and edit users; manage groups; assign a temporary password.
- Microsoft Graph — retrieve users by list, ID, or email.
- ClassLink OneSync — list users, classes, schools, and enrollments.
HR and people systems
- Workday — search workers and retrieve a worker's record.
- ADP — search workers and demographics, and list organization departments.
- Rippling — list workers, departments, work locations, teams, and employment types.
- Greenhouse — list candidates, applications, jobs, and offers.
Productivity and collaboration
- Google Workspace — create, edit, enable, disable, and delete users; manage groups; reset passwords.
- SharePoint — add, update, and delete items, and manage permissions.
- Confluence — list and retrieve pages, spaces, and attachments.
- Notion — retrieve databases, pages, users, and comments.
Calendar and meetings
- Google Calendar — create, search, and delete events.
- Outlook Calendar — create, search, and delete events.
- Google Meet — create and configure meeting spaces.
- Zoom — create, edit, and delete meetings.
Documents, forms, and signatures
- DocuSign — create an envelope to send a document for signature.
- PandaDoc — list documents and templates, and retrieve document details and status.
- Jotform — list forms and questions, and retrieve submissions and reports.
Project and work management
- Jira — retrieve issues, list issues by JQL, and read transitions, comments, and projects.
- Azure DevOps — retrieve work items, and list queries, projects, teams, repositories, and builds.
- Asana — list tasks, projects, and workspaces, and read task stories and tags.
- ClickUp — list workspaces, spaces, folders, lists, and tasks.
CRM
- HubSpot — list contacts, companies, deals, and tickets.
IT operations and security
- PagerDuty — list incidents, services, and on-call schedules.
- Tenable — list scans, assets, and vulnerabilities.
Asset and hardware
- Dell — retrieve asset information, warranty, and components.
Use cases
The value shows up when a single workflow coordinates steps that would otherwise be handled by different people in different tools.
-
Employee onboarding. One request reads the new hire's role and start date from Workday or Rippling, creates their account and group memberships in Entra ID or Google Workspace with a temporary password, books first-week orientation with a Google Meet or Zoom link, and sends equipment and policy agreements through DocuSign. Provisioning runs after the assigned manager approves, and every step stays on the same request.
-
Employee offboarding. On a departure date, the workflow disables the account, removes group memberships and content permissions across the identity platform and SharePoint, clears upcoming calendar events, and records completion for audit. Access closes the same day, with a full trail of what changed and when.
-
Software and access requests. A request reads the employee's current groups and application assignments from Okta, routes for approval based on what they already hold, and on sign-off adds them to the right group and applies the permissions. Access is granted after approval, and the full path stays on record.
-
Incident and vulnerability triage. A workflow pulls open incidents from PagerDuty and flagged vulnerabilities from Tenable, enriches the ticket with owner, severity, and asset context, and routes it to the on-call team. Prioritization runs on live data from the source.
In short
Built-in Action Connectors are about removing friction at the moment work needs to happen. Instead of stopping to configure web services or switching tools to finish a task, actions in external systems can now be added where they belong: inside the process.
The setup stays visual, the configuration stays simple, and teams don’t need technical expertise to make it work.
You can start using Built-in Action Connectors from the Workflows module in your InvGate Service Management instance, or explore them through a free trial and see how they fit into your everyday processes!