Chapter 5. Create integrations

1. Determine whether an application that you want to connect to uses the OAuth protocol. For each application that uses OAuth, register Fuse Online as a client that is authorized to access that application. Applications that use the OAuth protocol include:

   • Dropbox
   • Gmail
   • Google Calendar
   • Salesforce
   • SAP Concur
   • Twitter
2. Determine whether an application that you want to connect to uses HTTP basic authentication. For each application that does, identify the user name and password for accessing that application. You need to provide this information when you create the integration.
3. For each application that you want to integrate, create a connection.

Procedure

1. In the left panel in Fuse Online, click Integrations.
2. In the upper right, click Create Integration.

3. Choose and configure the start connection:

   1. On the Choose a Start Connection page, click the connection that you want to use to start the integration. When this integration is running, Fuse Online will connect to this application and obtain data that you want the integration to operate on.
   2. On the Choose an Action page, click the action you want this connection to perform. The available actions vary for each connection.
   3. On the page for configuring the action, enter values in the fields.
   4. Optionally, if the connection requires data type specification, Fuse Online prompts you to click Next to specify the input and/or output type of the action.
   5. Click Done to add the start connection.

   As an alternative to connecting to an application, a start connection can be a timer that triggers integration execution at intervals that you specify or it can be a webhook that accepts HTTP requests.

4. Choose and configure the finish connection:

   1. On the Choose a Finish Connection page, click the connection you want to use to complete the integration. When this integration is running, Fuse Online will connect to this application with the data that the integration has been operating on.
   2. On the Choose an Action page, click the action you want this connection to perform. The available actions vary for each connection.
   3. On the page for configuring the action, enter values in the fields.
   4. Optionally, if the connection requires data type specification, Fuse Online prompts you to click Next to specify the input and/or output type of the action.
   5. Click Done to add the finish connection.

   As an alternative to connecting to an application, a finish connection can send information to the integration’s log about the messages that the integration processed.

5. Optionally, add one or more connections between the start connection and the finish connections. For each connection, choose its action and enter any required configuration details.
6. Optionally, add one or more steps that operate on integration data between connections. See About adding steps between connections.
7. When the integration contains all needed steps, click Save as Draft or Publish according to whether you want to start running the integration.
8. In the Integration Name field, enter a name that distinguishes this integration from any other integrations.
9. In the Description field, enter a description, for example, you can indicate what this integration does.
10. If you are ready to start running the integration, in the upper right, click Publish. Otherwise, click Save as Draft.

Procedure

1. In the left panel, where you want to add a data mapper step, hover over the .
2. In the popup that appears, click Add a Step.
3. On the Choose a Step page, click Data Mapper to display source and target fields.

Procedure

1. In the left panel, where you want to add a filter step to the integration, hover over the and in the popup that appears, click Add a Step.
2. On the Add a Step page, click Basic Filter.

3. On the Configure Basic Filter Step page, in the Continue only if incoming data match field, select one of the following options:

   • Accept the default that all defined rules must be satisfied.
   • Indicate that only one rule must be satisfied by selecting ANY of the following.

4. Define the filter rule:

   1. For this field: In the field on the left, enter the name of the field that contains the content you want the filter to evaluate. For example, suppose the data coming in to the step consists of tweets that mention your Twitter handle. You want to continue the integration only when the tweet contains certain content. The tweet is in a field named text so you enter or select text as the value in the first field.

      You can define the field value in the following ways:

      • Start typing. The data name field has a typeahead feature that provides a list of possible completions for you in a pop-up box. Select the correct one from the box.
      • Click in the text field. A dropdown box appears with a list of available fields. Select the field of interest from the list.
   2. This condition must be satisfied: In the middle field, select a condition from the dropdown box. The setting defaults to Contains. For the integration to continue, the condition that you select in this field must be true for the value that you enter in the third field.
   3. For this value: In the third field, enter a value to filter on. For example, if you want to operate on mentions of a certain product from the Twitter feed, you would enter the product name here.

5. Optionally, click + Add another rule and define another rule.

   You can delete a rule by clicking the trash can icon next to the entry.

6. When the filter step is complete, click Done to add it to the integration.

Procedure

1. In the left panel, where you want to add an advanced filter step to the integration, hover over the and in the popup that appears, click Add a Step.
2. Select Advanced Filter.

3. In the edit box, use the Camel Simple Expression language to specify a filter expression. For example, the following expression evaluates to true when the message header’s type field is set to widget:

   ${in.header.type} == 'widget'

   In the following example, the expression evaluates to true when the body of the message contains a title field:

   ${in.body.title}

4. Click Done to add the advanced filter step to the integration.

Procedure

1. In the integration visualization panel on the left, hover over the at the location where you want to add a log step.
2. In the popup, click Add a Step.
3. On the Choose a Step page, click Log.

4. On the Configure Log Step page, select the content that you want to log. If you select Custom text, then in the text input field, enter one of the following:

   • The text that you want to log
   • A Camel Simple language expression

   If you enter an expression, Fuse Online resolves the expression and logs the resulting text.

5. When log step configuration is complete, click Done to add the step to the integration.
6. When the integration is complete, publish it to start seeing output from the new log step.

Procedure

1. In the integration visualization panel on the left, hover over the at the location where you want to add a template step.
2. In the popup, click Add a Step.
3. On the Choose a Step page, click Template. The Upload Template page opens and prompts you to choose how you want to define the template.

4. To define the template, do one of the following:

   • Drag and drop a template file or a file that contains text that you want to modify to create a template, into the template editor.
   • Click browse to upload, navigate to a file, and upload it.

   • In the template editor, start typing to define a template.

     Note that you might upload a template that is valid in other environments but that has errors in Fuse Online. Fuse Online requires that you append the body. prefix to each placeholder inside double curly braces. For example, while {{text}} is valid in a typical template, you must specify {{body.text}} in a template that you use with Fuse Online. Here is an example of a valid template:

   At {{body.time}}, {{body.name}} tweeted:
   {{body.text}}

5. In the template editor, ensure that the template is valid for use with Fuse Online. Fuse Online displays to the left of a line that contains a syntax error. Hovering over a red indicator displays hints about how to resolve the error.

   Inside each set of double curly braces, the body. prefix is required. Data mapping does not work if the body. prefix is missing. For example, if you upload a template that does not have the body. prefix on each placeholder, Fuse Online displays an error icon on those lines.

6. Click Done to add the template step to the integration.

   If the Done button is not enabled then there is at least one syntax error that you must correct.

   Input to a template step must be in the form of a JSON object. Consequently, you must add a data mapping step before a template step.

7. To add a data mapper step before the template step:

   1. In the left panel, hover over the that is immediately before the template step that you just added and then click Add a Step.
   2. On the Choose a Step page, click Data Mapper.

   3. In the data mapper, map a source field to each template placeholder field.

      For example, using the template above, map a source field to each of these template fields:

      • body.time
      • body.name
      • body.text
   4. In the upper right, click Done to add the data mapper step to the integration.

   Output from a template step is always a JSON object. Consequently, you must add a data mapper step after a template step.

8. To add a data mapper step after the template step:

   1. In the left panel, hover over the that is immediately after the template step you just added and then click Add a Step.
   2. On the Choose a Step page, click Data Mapper.
   3. In the data mapper, map the template’s message field, which always contains the result of inserting source fields into the template, to a target field. For example, suppose that a Gmail connection is next in the integration and you want to send the result of the template step as the content of a Gmail message. To do this, you would map the message source field to the text target field.
   4. In the upper right, click Done.

Procedure

1. In the left panel, where you want to add a custom step to the integration, hover over the and in the popup that appears, click Add a Step.

2. On the Add a Step page, click the custom step that you want to add.

   The list of available steps includes any custom steps that are defined in extensions that were uploaded to your Fuse Online environment.

1. Respond to prompts for any information that is required to perform the step. This information varies for each custom step.