amaralli

Keybase proof

I hereby claim:

• I am amaralli on github.
• I am amaralli (https://keybase.io/amaralli) on keybase.
• I have a public key ASDmzfPdZVBuCIhpubU-_rnoBfNitZl3LviLEBLnceuhWwo

To claim this, I am signing this object:

amaralli

Control Assign If

Assign a value based on the output of an expression.

Inputs

• left-operand: The first operand in the expression.

• operator: The operator to compare two values in an expression.

amaralli

#Multipart Form-Data FS

Disclaimer : This is work in-progress documentation. Largely stolen from Kevin, with some additions by me. This will be referring to Box's "Upload File" API endpoint. Documented here.

1. Anatomy of a Multipart Form-Data Request
2. General Structure
3. Doing this in Forge
4. Testing

##Anatomy of a Multipart Form-Data Request

amaralli

#Getting Started ##What is a Connector? A Connector is an interface that communicates with external APIs. The goal of a Connector is not to be a direct reflection of an API, but instead a user-friendly abstraction on top of an API. Connector development is more focused on end-user needs than on the capabilities of the API. Each Connector 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 Connector, you must write a Connector 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 Connector JSON file is to lay out in a linear manner the pre-defined action steps (known as modules) that will execute ea