Personalizing Your Integrations tries its best to automatically determine how different services should integrate, but sometimes you'll want to create an integration that's tailored just for you.  This is called a Personalization, which is a way of mapping the output of an action on your bip, as the input of another action on your bip.

A Personalization needs at least a source and destination node to operate.  Let's take a look at an example where we create a personalized Email from a Twitter search result.

After making a connection between the services, create the Personalization by double-clicking on the destination action

 Double Clicking the destination (email) icon will reveal a Personalization screen.  The Personalize screen lets you take the attributes from previous actions and map them to attributes on the selected destination service.

The input fields can be a mixture of text and attributes in whatever way makes sense to you.  To map a variable, either press Ctrl+i while editing with your keyboard, or the '+ Attributes' button to insert at the current cursor position.

The dropdown which appears is a set of searchable attributes which can be placed into your template.  Any actions appearing earlier in your integration may also provide their attributes here.

Lets look at a complete Twitter Feed > Email integration :

Custom Fields vs Preset Fields

Some integrations require values which have certain constraints, such as a Facebook Page ID's for your specific account, or the name of a network device you manage.  These service specific values are presented as Presets and are savable for easy re-use.

To save a Preset, simply set your preset values in the Personalization form, and hit Save Presets.  You can set a custom value for the attribute by pressing the 'Custom' button.

Required Fields

Fields that are required are marked by , when the field has been populated it will show 

Important :  Because attributes can come from any other connected action, a required field marked as populated is only a guarantee that the integration might work.

Naming Actions

Actions get their default names from the action they perform.  To rename an action in a Bip, click the edit icon next to the action name in the personalizations to edit.

Ad-Hoc Data

Sometimes it's necessary to mix and match variables appearing from arbitrary services (such as Web Hooks or the HTTP Requests Pod), but they usually won't be available in the 'Attributes' list.  To learn how to map unknown attributes, see the developer documentation in the Open Source Wiki, or in the case of discovering attributes from Incoming Web Hooks, see the Request Parser section of How To Create A Web Hook

Feedback and Knowledge Base