Skip to main content

Integrations

General overview of integrations in Actioner.

Actioner is a web-based automation tool that allows users to connect different applications and services to create automated workflows. Integrations in Actioner are created using pre-built connectors and can be customized with filters and actions to perform specific tasks.

What is an integration in Actioner?​

An integration in Actioner refers to the connection between two or more applications, allowing data to be transferred and actions to be triggered between them. Integrations are built using pre-built connectors that are connected through a workflow in Actioner.

How it works​

Integrations in Actioner work by using triggers and actions. Triggers are pre-built components that monitor for changes in an application or service, such as a new contact being added to a CRM system or a new email arriving in an inbox. When a trigger is activated, it initiates a workflow that includes one or more actions. Actions are pre-built components that perform specific tasks in an application or service, such as creating a new contact or sending an email.

When building a workflow in Actioner, users can select a trigger from a list of available options and configure it with the appropriate authentication details. They can then choose one or more actions to perform when the trigger is activated and configure the input data for each action. Once the workflow is configured, it can be activated and will run automatically whenever the trigger is activated.

Features of integrations in Actioner​

Some of the key features of integrations in Actioner include:

  • Pre-built connectors for various applications and services
  • Actions and triggers with pre-defined filters
  • Real-time data transfer between applications and services
  • Automatic error handling and retrying of failed tasks

Components of integrations in Actioner​

The two main components of integrations in Actioner are triggers and actions.

Triggers​

Triggers are pre-built components that monitor for changes in an application or service. When a trigger is activated, it can initiate a workflow that includes one or more actions. Some examples of triggers in Actioner include:

  • New contact added to a HubSpot account
  • New email received in an inbox
  • New tweet posted on Twitter

Actions​

Actions are pre-built components that perform specific tasks in an application or service. When an action is triggered, it performs the specified task in the connected application or service. Some examples of actions in Actioner include:

  • Creating a new contact HubSpot system
  • Sending an email
  • Posting a message on a Slack channel

Examples of integrations​

Zendesk integration​

The Zendesk integration in Actioner allows users to create, update, and retrieve tickets, users, and organizations in Zendesk directly from Actioner. This integration can be used to automate customer support workflows and improve response times.

To use this integration, users can select the Zendesk trigger that monitors for new tickets or updates to existing tickets, and then choose one or more actions to perform when the trigger is activated. For example, users can create a new ticket in Zendesk when a new email is received in an inbox.

Hubspot integration​

The Hubspot integration in Actioner allows users to create, update, and retrieve contacts, companies, and deals in Hubspot directly from Actioner. This integration can be used to automate sales and marketing workflows and improve lead generation and management.

To use this integration, users can select the Hubspot trigger that monitors for new contacts or updates to existing contacts, and then choose one or more actions to perform when the trigger is activated. For example, users can create a new contact in Hubspot when a new lead is added to a CRM system.