chelseasanc

swagger: "2.0"
info:
  description: API for managing an environment's connectors
  version: 0.1.0
  title: Connector Management API
host: connectormgmt.*ui.azuqu3a.com
basePath: /api
tags:
  - name: connectors
    description: The connectors available in the environment

chelseasanc

{
  "brick": "http",
  "config": {
    "method": "POST",
    "url": "https://azuqua.uservoice.com/api/v1/users.json",
    "headers": {
      "Authorization": "Bearer {{auth.access_token}}"
    },
    "body": {
      "user[display_name]": "{{{input.lookuprequest.displayName}}}",

chelseasanc

Table of Contents

What is a Channel?

A Channel is an interface that communicates with external APIs. The goal of a Channel is not to be a direct interface that sits on top of an API, but instead a user-friendly abstraction on top of an API. Channel development is more focused on end-user needs than on the capabilities of the API. Each Channel is made up of methods, which appear to the user as the different Event and Action cards. Each method determines how data is fetched from the API, and transforms data to the user-friendly format accepted by the front-end. Most methods use more than one API call to do this.

To define a Channel, you must write a Channel JSON file and submit this file to Azuqua for upload into the engine. At runtime, the engine will access the instructions laid out in this file to execute the Event or Action the user has designated in their Flõ. The primary function of a Channel JSON file is to lay out in a linear manner the pre-defined action steps (known internally as bricks) th

chelseasanc

Getting Started

What is a Channel?

A Channel is an interface that communicates with external APIs. The goal of a Channel is not to be a direct reflection of an API, but instead a user-friendly abstraction on top of an API. Channel development is more focused on end-user needs than on the capabilities of the API. Each Channel is made up of methods, which appear to the user as the different Event and Action cards. Each method determines how data is fetched from the API, and transforms data to the user-friendly format accepted by the front-end. Most methods use more than one API call to do this.

To define a Channel, you must write a Channel JSON file and submit this file to Azuqua for upload into the engine. At runtime, the engine will access the instructions laid out in this file to execute the Event or Action the user has designated in their FLO. The primary function of a Channel JSON file is to lay out in a linear manner the pre-defined action steps (known internally as bricks) that will execute ea