A Pipeline is constructed from simple steps called pipes. A Pipeline is the link between your applications. For example - send a “New Message on Slack” when a “New Lead is created in Salesforce” is what is contained in a pipeline.
A Trigger is an event that can make a pipeline run. For example, if you want to automate sending a slack message every time a new Lead is created in Salesforce, then “New Lead Created” is the Trigger. Cloudpipes also supports pipelines that do not have trigger. Such pipelines can be started either manually, for on-off tasks or can be scheduled to be automatically run on set intervals.
Actions do stuff - send messages, create records in Salesforce, translate text to another language or just about anything that your apps are capable of. For example, if you’re sending that slack message, every time a new Lead is created in Salesforce, the “Post Message to Slack” is the Action.
Pipes are the building blocks of pipelines. Each pipe belongs to a certain channel and is responsible for doing something - creating a record in Salesforce, uploading a picture or sending an email with Google.
A Pipe can be either a Trigger or an Action. For example “Send a Message on Slack” is an action pipe and “New Lead Created in Salesforce” is a trigger pipe.
Blueprints are pre-composed pipelines that are ready to use. You just need to add them to your Dashboard and add your Accounts for the relevant services. Blueprints save time, eliminate pipeline building errors and help tremendously in getting your apps talk to each other.
An Account allows Cloudpipes to access your data inside another app. Each service like Slack, Salesforce or GMail needs to have an account configured in Cloudpipes in order to be used in building pipelines.
Fields are the attributes of data flowing though the pipelines. A Trello Card name for example is a field, so is the Value of a Salesforce Opportunity and the Due Date of an Asana Card. In the Editor Fields are color-coded by type. For reference see Field Colors Guide.
The Cloudpipes Editor is where you create and edit your pipelines. The Editor is simple to use, allowing you to build complex integrations by simply dragging and dropping Triggers and Actions from the palette on the right.
The Dashboard is where you have an overview of all your existing pipelines, your account and billing data and usage reports.
An Application in the context of Cloudpipes is a web service or application. Salesforce , Slack, Trello and Asana are all web applications. Cloudpipes supports hundreds such applications, allowing you to connect and automate them.
A Channel represents an Application that has support implemented in Cloudpipes. A Channel is a collection of pipes that represent the Triggers and Actions supported by the Applicaton implementing them. For example Salesforce is a channel in Cloudpipes - a collection of Pipes that represent what you can with Salesforce, the Application in Cloudpipes. So are Slack, GMail, Trello and all the other Applications Cloudpipes supports.
Channels on Cloudpipes belong to either the Standard, Tier-1 or Tier-2 groups. Using channels from a certain group requires you to be on one of our paid plans. Click here for a list of channel per tier.
A Built-in Channels is a channel that does not have a backing web application, but instead has functionality provided entirely by Cloudpipes. RSS Feeds, NLP based text sentiment analysis, Webhooks are all examples of such channels. For a full guide on built-in channels see Built-in Channels Guide
A transaction is a successful execution of an action. For instance, if your pipeline creates new users in Intercom when there are new accounts in Salesforce, each action (user created) in that pipeline would count as a single transaction.