Generic Integrations

Generic Integrations allow you to interact with any third-party system that offers a REST API via username/password or token-based authentication.

Overview

EdgeIQ’s Generic Integrations feature allows users to store credentials for external systems directly within the EdgeIQ platform. These integrations enable the SymphonyIQ Workflow Orchestrator to interact seamlessly with any external service that supports username/password or token-based authentication. This means that users can go beyond the native integrations supported by EdgeIQ and connect to virtually any system with a compatible API.

Key Benefits

  • Flexible Authentication: Supports both username/password and token-based authentication methods, making it adaptable for various external services.
  • Connect to any system: Integrate with any system that offers a REST API, providing limitless integration options.
  • Orchestration: Credentials stored using Generic Integrations can be utilized within workflows using the Generic REST API node, allowing users to automate interactions with third-party systems effortlessly.

Creating a new Generic Integration

1. Navigate to the Integrations Section:

  • Go to the “Integrations” tab within your EdgeIQ account.

2. Create a New Integration:

  • Click on “Create New Integration”.

3. Fill in the Integration Details:

Create a new integration dialog

Create a new integration dialog

  • Integration Name: Enter a meaningful name for your integration (e.g., “ERP System”, “HubSpot CRM”).
  • Description: Optionally, add a description to help you remember the integration’s purpose.
  • Integration Type: Select one of the following:
    • Generic Username/Password Integration
    • Generic Token Integration

Username/Password-Based Authentication

Example: username / password authentication for an ERP system

Example: username / password authentication for an ERP system

When you select Generic Username/Password Integration:

  • Provide the username and password required by the external system.
  • These credentials will be stored in EdgeIQ and can be used in workflows where authentication is required.

Example Use Case: Connecting to an internal ERP system that requires a username and password to access its API.

Steps:

  • Enter the username and password in the designated fields.
  • Save the integration to store the credentials.

Token-Based Integration

Example: Creating an integration with a CRM like Hubspot via token authentication

Example: Creating an integration with a CRM like Hubspot via token authentication

When you select Generic Token Integration:

  • Enter the token provided by the external system.
  • This token will be securely stored and can be used by the SymphonyIQ Workflow Orchestrator for authenticated API requests.

Example Use Case: Integrating with CRM systems like HubSpot, which use token-based authentication to access their APIs.

Steps:

  • Copy the API token from your external service.
  • Paste it into the Token field.
  • Save the integration to store the token.

Example Workflow

Imagine you want to pull customer data from a CRM system that requires token authentication. Everytime a device report is received, the report should be enriched with data from the CRM.

Here’s how you can set up the workflow:

  • Create a new Generic Token Integration for your CRM.
  • In the workflow, add a Report In node to receive the device report.
  • In the workflow, add the Get Integration Details node and select your Generic Integration to pass the integration details to the next workflow node.
  • In the workflow, add a REST API Node. Configure the REST API node according to the specifications of the API of your CRM system. The REST API node supports all common HTTP methods, for example, GET or POST.

That's it! Now you can enrich your device data with external data from your CRM system!