Nembl
Developer Guide
Integrations

Integrations

Nembl integrates with external systems through its connector framework. Connectors enable workflows to send and receive data from third-party services, trigger actions in external tools, and synchronize state across platforms.

Available Connectors

Nembl ships with connectors for popular business tools:

ConnectorAuthenticationUse Cases
SlackOAuth 2.0Send messages, create channels, post workflow updates, receive slash commands
JiraOAuth 2.0Create issues, sync status, link Nembl requests to Jira tickets
GitHubOAuth 2.0 / PATCreate issues and PRs, trigger workflows on push/PR events, read repository data
ServiceNowOAuth 2.0Create incidents, sync CMDB data, bridge ITSM workflows
SalesforceOAuth 2.0Create and update records, trigger workflows from Salesforce events
HubSpotOAuth 2.0Sync contacts, trigger workflows from deal stage changes
OpsGenieAPI KeyCreate alerts, escalate incidents, sync on-call schedules
DocuSignOAuth 2.0Send documents for signature, track signing status, trigger workflows on completion
Microsoft TeamsOAuth 2.0Send messages, post adaptive cards, receive notifications
PagerDutyAPI KeyCreate incidents, trigger escalations, sync status
LinearAPI KeyCreate issues, sync status, bidirectional updates
Email (SMTP)SMTP credentialsSend formatted emails, attach documents, notification workflows
ChargebeeAPI KeySubscription events, invoice data, billing triggers
Generic REST APIAPI Key / OAuth / CustomConnect to any REST API with configurable authentication

Connecting an External System

Step-by-Step

  1. Navigate to Settings > Connectors.
  2. Click Add Connector.
  3. Select the connector from the catalog.
  4. Follow the authentication flow:
    • OAuth connectors -- click "Connect" and authorize Nembl in the external service's consent screen.
    • API key connectors -- enter your API key or token (stored as a secret).
  5. Configure connector-specific settings (e.g., default Slack channel, Jira project key).
  6. Click Save.

The connector is now available for use in workflows.

Testing a Connection

After setup, click Test Connection to verify that Nembl can communicate with the external service. The test performs a lightweight API call (e.g., listing channels in Slack, fetching user info from GitHub) and reports success or failure.

Using Connectors in Workflows

Once a connector is installed, it appears in the workflow builder as an available action type.

Adding a Connector Action to a Workflow

  1. Open a workflow in the builder.
  2. Add or edit a phase.
  3. In the phase configuration, click Add Action.
  4. Select Connector Action.
  5. Choose the connector (e.g., Slack).
  6. Select the action (e.g., "Send Message").
  7. Configure the action parameters, mapping workflow variables to the action inputs:
Connector: Slack
Action: Send Message
Channel: #engineering-alerts
Message: "New request {{ request.title }} from {{ request.createdBy.name }}"
  1. Save the phase configuration.

Variable Mapping

Connector actions can reference workflow variables using the {{ }} syntax:

VariableDescription
{{ request.id }}The current request ID
{{ request.title }}Request title
{{ request.priority }}Request priority
{{ request.createdBy.name }}Name of the requester
{{ request.fields.* }}Custom form field values
{{ phase.name }}Current workflow phase name
{{ workflow.name }}Workflow name

Custom REST API Connector

For services without a dedicated connector, use the Generic REST API connector.

Configuring a Custom Integration

  1. Navigate to Settings > Connectors > Add Connector > Generic REST API.
  2. Configure:
    • Base URL -- the API's base URL (e.g., https://api.example.com/v1).
    • Authentication -- choose API Key, OAuth 2.0, Bearer Token, or Basic Auth.
    • Default headers -- headers sent with every request.
  3. Save the connector.

Using in Workflows

When adding a Generic REST API action to a workflow:

Method: POST
Path: /tickets
Headers:
  Content-Type: application/json
Body:
  {
    "title": "{{ request.title }}",
    "description": "{{ request.fields.description }}",
    "priority": "{{ request.priority }}"
  }

The response body is available as a workflow variable for subsequent phases.

Connector Permissions

Connector access is governed by the policy engine. Admins can control:

  • Who can install connectors -- connectors:create permission.
  • Who can configure connectors -- connectors:update permission.
  • Who can use connectors in workflows -- connectors:read permission (required to select a connector in the builder).

Best Practices

  • Use OAuth when available. OAuth provides scoped, revocable access and is more secure than long-lived API keys.
  • Test connections after setup. Verify the connection works before using it in production workflows.
  • Use the Generic REST connector sparingly. Dedicated connectors handle authentication, pagination, and error handling automatically.
  • Monitor connector health. Check for failed actions in the workflow execution history and reconnect if OAuth tokens expire.
  • Limit connector permissions. In the external service, create a service account with minimal permissions for the Nembl integration.
MCP ServerAI Agents