Remote Conditions and Web Hooks

Chris Quiroz -

FluidReview has the ability to securely communicate with remote servers via Remote Conditions and web hooks. These two features work in tandem with our Triggers system to expand the functionality of FluidReview's decision-making and task automation abilities.

Here's a breakdown of the parameters, and an example use case for each new feature:

Remote Conditions

Remote Conditions allow you to program a Trigger in FluidReview that will only execute if a certain condition is received back from a specified remote server.

For example: If you want your FluidReview site to ascertain if a certain student number is exempt from providing a certain document in your application process, you can send a query to a remote database that effectively asks this question. Depending on the response received, you can program your FluidReview site to act accordingly by either requesting this document or not.

  •  URL

This is the URL of your remote server.

  • Method:

Set this to either GET or POST, depending on the requirements of your remote server.

  • Source:

This drop-down menu is pre-populated with the variables from your FluidReview forms. Select the variable that should be evaluated by the remote server.

  • Value:

Input the value you expect to receive from the remote server to indicate a successful trigger.

  • Auth Token:

Optionally, you can input an authorization that will be passed to your remote server.

Web Hooks (Remote Actions)

If the condition of any given Trigger is met, you can instruct FluidReview to execute a number of actions, one of which is the new web hook. A web hook will instruct FluidReview to contact a remote server, which can in turn perform an external task.

For example: If you successfully process an application from a new applicant, you can instruct FluidReview to contact your external database server to update a record. This could be useful if you wanted to dynamically update a job opening posted on your corporate website after an application has been accepted by your FluidReview site.

 

  1. URL

This is the URL of your remote server.

  1. Method:

Set this to either GET or POST, depending on the requirements of your remote server.

  1. Source:

This drop-down menu is pre-populated with the variables from your FluidReview forms. Select the variable that should be passed to the remote server.

  1. Auth Token:

Optionally, you can input an authorization that will be passed to your remote server.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.