Services — Features list of each service

Flow services let us connect our apps to other applications, service providers, or databases. We can also use services to extend the functionalities of a flow (say, to delay the flow, or schedule a task) and for end-user authentication.

Let’s take a look at the features supported by Flow services:

  • Identity: For many customers, you will already have a directory of users in place. This allows you to re-use your existing identity system rather than creating yet another user repository.
  • Location: Lets you tap into location services.
  • Views: Currently under development.
  • Social: The ability to embed a social network feed into your application. Currently, works with Chatter in Salesforce.
  • Messages: The ability to interact with the service using the message element.
  • Files: The ability to expose files stored in an external repository from within your Flow applications. This also allows users to upload and manage files through flows.
  • Auto binding: Currently under development.
  • Database: The ability to connect to a remote data source and perform save, load and delete operations.

Here is a list of Flow services, and the features each service supports.

Service Identity Location Views Social Messages Files Auto binding Database
Identity Yes Yes No No No No No No
Box Yes No No No Yes Yes No Yes
Email No No No No Yes No No No
PDF No No No No Yes No No No
Salesforce Yes No No Yes Yes No No Yes
SharePoint Yes No No No No Yes No Yes
SQL No No No No No No No Yes
Timer No No No No Yes No No No
Twilio No No No No Yes No No No
Boomi Flow Ninja // 
  1. When you are building your service integration, think of functionalities as distinct buckets like Database, Identity, Logic, Social, or Files. This will help you think about the features of the API, and where they best fit. Example: This is a CRUD object/API, I need to use the Database features in the SDK. This is a business logic that needs to be implemented in the service code, I need to use the Logic features.
  2. The Flow Service component gives you access to AtomSphere’s visual interface. Enter the required metadata, create a process to implement the service actions, and deploy the Flow Service component in a process. Refer to the AtomSphere process by providing the URL in a flow.