- Web Service:
A web service communicates between machines, not human users, over a network. Its interface uses a machine-processable format (specifically WSDL). Other systems interact with the Web service using SOAP-messages, typically conveyed using HTTP with XML in conjunction with other Web-related standards. Cloudsnap often establishes connections through web services when SOAP APIs are transmitted.
Persistent bidirectional communication channel between a browser (client) and backend service. Unlike an HTTP API Call, a web socket can transport various protocols and deliver messages between server and client without polling.
One of four trigger types that initiates a workflow instance. When a workflow uses a webhook, an event in the trigger application starts each instance. The event automatically pushes data into the payload for processing then posting in the connected application. The webhook provides near-real-time updates to the connected application.
Set of steps that represent a technical process. The steps define the data used in the process and how to transfer data from a source application to prepare it for a destination application. Initiated by a trigger, the workflow can reformat or recalculate data as it passes through each step in order. (See Trigger.)
- Workflow Instance:
Single run of a general workflow.
- Workflow Logs:
- Workflow Steps:
Events, or actions, that occur within a workflow: GET or POST in an API Call, transform JSON, and more.
- Workflow Template:
Generic framework used to reduce workflow development time for common date transfers between frequently connected apps.
- Workflow Variables: