How to integrate your apps in 1 click?

Integrately makes it really easy to integrate your apps.

  1. Select the apps to integrate
  2. Integrately shows you various popular automations
  3. Select your automation.
  4. Integrately creates the automation for you. Even mapping.
  5. Just test it and make it live!

Isn't that awesome?

 

Let's do this step by step.

  1. Click on explore & automate
  2. Select the apps you want to integrate
  3. Integrately will automatically bring to you a list of ready automations for the two selected apps. No need to waste time in creating automation. Just browse through the list and look for the ones that you need.
  4. Click on the automation you are looking for. And ta-da! Your integration is ready to be used.

Just 1 click! That's all it took to integrate the two apps.

 

If you have found the integration you were looking for, skip the next section & jump to the next step of setting up connection between Integrately and the chosen apps. However, if you couldn't find what you were looking for, see the next section to learn how to make your own integration in a few easy steps

What if I don't see my automation in 1 click integrations?

Not necessary you will find all the automations readily available. Sometimes you may have a particular requirement, other than the popular ones.

custom integration

 

For example, you want to create an automation where-in if a contact has subscribed to an email sequence in ConvertKit, a deal is automatically created in CompanyHub.

 

To create this automation, you need to follow 2 easy steps:

  1. First, we need to select the relevant “when” condition. To do so, browse through the drop down list in “when this happens” and select the required condition.

    select trigger
  2. Next you need to select the “then” condition. This can be done by browsing through the drop down menu in “Do this” and selecting the relevant outcome

    select action
  3. Now that you have selected the when and then of your integration, you are good to go. Just click on the “Go” button and your integration is ready.

Add Accounts

Connect your apps in Integrately so we can sync them. Click on 'Add Connection' to connect your apps in Integrately

add connection

If you have already connected your apps with Integrately, just select from the list.

add connection

Follow the instructions or process to connect your accounts. In most cases, you will find a step-by-step video or set of instructions to connect your account with Integrately.

Field Mapping

In the simplest form, Integrately takes data from your source app and gives to your destination app.

 

But the field in both apps will probably be different. For each field in the destination app, you can select the corresponding field of source app.

 

We call this as Field Mapping.

 

In most cases, we try to smartly create mapping on our own.

 

But if you want, you can map additional fields. Or, edit the default mapping as per your requirements.

 

Follow these steps to map fields or make any changes to the existing mapping -

  1. Click on the field you want to map in the destination app
  2. There are 3 ways to map a field:
    • You can select the field from the source app that you want to sync with this particular field, or
    • You can also select from the fields in the ‘Fixed’ section, which will display a pre-defined list to pick from, depending on the field to be mapped, or
    • You can also manually set the value of the field and click ‘Enter’

You can also set fixed value for a field

Or modify the data before passing to to destination app

Test & go live

Once the mapping is complete, you will need to ‘test’ your automation. To check whether it is giving the desired result or not.

 

How to check your automation?

 

Click on the ‘Test and Go live’ button. Now Integrately will pull the sample form you see while activating the automation, and send it to the destination app to produce the desired record. If it is successful in doing so, Integrately will notify you about the successful implementation of the automation.

 

You can now check the destination app for the newly created record

 

However, sometimes it may happen that your automation will be activated successfully, but you may not see any records getting created in the destination app. In that case, Integrately will notify the occurrence of an error. You then need to revisit your field mapping and make the required changes.

 

For additional satisfaction:

 

Despite seeing the test record being created, sometimes you may feel the need to test the automation yourself. In that case, you can create a record in the source app for the desired ‘when’ condition yourself.

Then you need to wait for a few minutes for it to reflect in the destination app. Once you can see a new record is created in the destination app, you can be rest assured that your automation is fully functional now.

Managing your automations

Integrately lets you sort and organize your automations.

 

After setting up the automation, Integrately lets you choose the folder you want the automation to be stored in. You simply need to select from the drop down menu.

Integrately even lets you -

  • Add new folders,
  • Change the default folder, or
  • Rename a folder to suit your requirements

If you want to sort and organize your automations in different folders, you simply need to follow 3 steps.

 

  1. Select the automation
  2. Click the ‘Move to’ button.
  3. Select the desired folder from the drop down list.

It's that easy!

 

However, if you wish to delete a particular folder, you first need to move all its automations to another folder before deleting it. You cannot delete a folder if it has any automation stored in it.

Modify data

Sometimes you want a different format for the data in your destination app. Meaning, you want to change the format of your output app as opposed to the source app.

 

Integrately gives you this freedom. It lets you change the format of your input data be it text, numbers or date. You can even add formula to a field. All this in just a few clicks while mapping the fields. No need to use any other app.

 

Let's have a look at few examples for when and how to use ‘Modify data’:

 

Handling Date formats

  1. Shift Date

     

    Suppose you want to set the follow up date for a lead as 3 days from the date of creation of the lead. So in that case, you need to use this modifier.

  2. Change Date Time from one format to another

     

    Suppose your source app shows date in dd/mm/yyyy format and you want the destination app to show date in dd-mmm-yy format. So you apply the above modifier to the relevant date field(s).

  3. Change date time to specified format

     

    Many times, the app accepts the date only in a particular format. For example, your destination app Google Calendar, which accepts the date in only this format - yyyy-MM-ddTHH:mm:ss So, here you need to use the above modifier.

  4. Current Time (When Automation is executed)

     

    Suppose your automation says - when a subscriber is added to your marketing automation, create a deal in your CRM.

     

    Now, you want the record in CRM to show the time of creation of the record to be the time of execution of the automation in your time zone.

     

    In other words, if you want the output to be something like this -

     

    In that case, you need to use the below modifier -

  5. Current Time & Timezone (When Automation is executed)

     

    Suppose your automation says - when a subscriber is added to your marketing automation, create a deal in your CRM.

     

    Now, you want the record in CRM to show the time of creation of the record to be the time of execution of the automation in your time zone. Additionally, you want the timezone to be displayed.

     

    In other words, if you want the output to be something like this -

    In that case, you need to use the below modifier -

  6. Change date from one timezone to another

     

    The timezone of any 2 apps exchanging data may or may not be in different timezones. Hence, to avoid confusion, every app treats the received timezone to be UTC.

     

    So, what happens is that the destination app treats the incoming time to be in UTC and then converts this time into the timezone selected by you. As a result, if your destination app timezone is UTC +5.3 hrs, the resultant time shown in the destination app will be UTC+11 hrs.

     

    So for example, your trigger app, say CompanyHub, is in UTC+5.30 timezone. And you want to pass the date to your trigger app, say ClickUp. So, in order to handle this, you need to use the following modifier -

  7. Convert Date Time to Unix format

     

    Suppose your destination app accepts date and time in UNIX format only (which will be mentioned alongside the DATE field in the app. Then you need to use this modifier.

  8. Convert Unix Time to Normal Date Time

     

    Suppose your source app, say ClickUp, sends the date in a format like this - 1593978425 (UNIX). But your destination app needs the date to be in normal format. In that case, you need to use this modifier.

 

Handling Text formats

  1. Change from Technical to human readable

     

    Suppose your source app saves the Company Id as ‘emilia_peels_montogmery’. But you don’t want to see the filename as ‘emilia peels montgomery’ in the destination app.

     

    So you apply the above modifier to the relevant field(s).

  2. Extract text till a specified character

     

    Suppose you want to map the identification field in your destination app with the email from the source app. But you only want to use the text before the "@" symbol. So you apply the above modifier to the relevant field(s).

 

Handling Number formats

  1. Calculate fields

     

    Suppose you want to auto calculate the billing amount for the product(s) in the invoice. So, what you can do is just select the product quantity field while modifying data and state the formula.

  2. Round off the number

     

    Suppose you received the value in the format 21.2364, but you want to round off the number to the closest number. Then you need to use this modifier. This modifier gives you 3 options for rounding off. You can choose the 1 you want.

  3. Round off to decimal

     

    Suppose you received the value in the format 21.2364, but you want to round off the number to 2 decimal places. Then you need to use this modifier.

  4. Convert to Absolute value

     

    Suppose you received data in the format -11, but you want to send it to the destination app as on 11. Then you need to use this modifier.

  5. Currency conversions

     

    Suppose you have customers from across the globe. But you want a single currency to be used for billing purposes, let's say GBP.

  6. Formatting number according to currency

     

    Suppose you receive the amount in the format 10000 and you want to convert it Indian format 10,000.

     

    So you need to use the modifier -> Format number according to country
    For Culture you can use -> en-IN

    Output -

  7. Formatting currency according to country

     

    Suppose you wish to add the currency symbol before the amount, say rupee symbol before the amount 10000

     

    So you need to use the modifier -> Format currency according to country
    For Culture you can use -> en-IN

    Output -

     

    *Note: You can use Google to find the Culture code for any country. For helping you understand what a particular culture codes looks like, you can refer to the the document shared on the below link - https://docs.google.com/spreadsheets/d/1shet22s_og3OPnPOhse-H39SRy3g1r9Kc5BYiuz8TGM/edit?usp=sharing

     

    Below is a glimpse of some of the currencies shared in the sheet -

     

    You can use Google to find the Culture code for any country

     

    You can modify any no. of fields in a single go. No need to go to every field individually and do the entire process again and again. Just do all of them at once.

     

    *Unless you are using the same field for applying different modifiers

 

Adding Multiple Modifiers

 

Suppose you want to use 2 modifiers before using it for mapping in the destination app. So, for this, we have added a separate app called ‘Data Modifier’.

 

For example, first you want to format the number as per Indian number system and then add the Rupee symbol to it.

 

In that case, you will need to add this before the destination app like this -

 

And the process would be as follows -

 

Editing the Modifiers

 

Sometimes after validating the modifier, you may feel that you don’t want to modify the data. In that case,

  1. If you have used modifier just once, simply click on ‘Don’t Modify Data’

  2. If you have used multiple modifiers, just cancel the unwanted modifier(s) and click ‘Validate & save’

Customizing your automation (Adding conditions/multiple apps)

Integrately lets you customize your automation to suit your requirements. For starters, you can rename your automation.

 

Furthermore, you can customize your automation to include more than 2 apps, or execute automation based on filters and even add ‘if-else’ conditions to handle different scenarios in a single automation.

 

To set-up the additions, you need to follow the below steps:

  1. Click on the ‘Modify Conditions and Actions’ button. It will switch from ‘test’ view to ‘flow’ view.

  2. Sometimes you may want to make additions somewhere in-between the automation and sometimes at the end of the automation. So you need to click on the ‘Add Condition/App’ button accordingly.

    • If you want to add at the end of the automation, hover on the ‘Add Condition/App’ button at the bottom and click on the relevant option.

    • If you want to make additions somewhere in-between the automation, hover on the app after which you want to make the addition. Then hover on the ‘Add Condition/App’ button and click the relevant option.

    Now the biggest question is, what is this relevant action?

  3. To add app(s): click on ‘Do something’

    Click here to learn more on how to add multiple apps to the automation.

  4. To create filter(s): click on ‘Check condition after this’

    Click here to learn more about filters.

  5. To add branching ( IF .. THEN …. ELSE .. kind of scenarios):

    • To set the ‘if’ condition, follow the same steps as creating ‘filter’

    • To set the ‘else’ condition, choose from the options in ‘if this condition is satisfied’ or click on ‘Else do something’

    • You can also add more branches to your ‘if - else’ condition. To do so, just add more filter(s) or app(s)

      Click here to learn more about branching.

Connect 3+ apps in an Automation

Sometimes you want to add more than 2 apps in the automation.

 

For example, you want to create an automation where

  • When a subscriber is added to a list in MailChimp

    • Create a deal in CompanyHub, and

    • Create a proposal in Better Proposal

 

To begin with, you need to select MailChimp and any 1 of the remaining apps. You can then add the last app depending on its location in the automation.

Your automation will be saved automatically. Now you need to ‘add connection’ for all your latest app additions to the automation and do the field mapping, before you ‘Test and Go live’.

 

Using data of different apps:

 

When you are using more than 2 apps in the automation, you can map fields for an app from any of the preceding apps in the automation.

 

For example, you want to create an automation where

 

  • When a subscriber is added to a list in MailChimp

  • Then create a deal in CompanyHub, and

  • Then create a proposal in Better Proposal

 

In that case,

  • for CompanyHub, you can map fields from MailChimp;

  • for Better Proposal, you can map fields from either MailChimp or CompanyHub or both.

Filter records

In some cases, you want to continue with the automation only if certain conditions are met. Like execute only if the deal stage is Won. So you can add a condition step. This condition can be placed anywhere in the automation.

 

Let’s use an example to understand this better. Suppose you want to create an automation where:

 

When a deal is updated in CompanyHub:

  • If deal stage is updated to won
    • Create a customer in QuickBooks Online

 

So once you have set the filter in CompanyHub, unless the updated deal stage contains the words ‘won’, the customer will not be created in QuickBooks Online.

 

Let’s look at the different kinds of filters and their implications -

  1. Exactly Matches

     

    This means that the next step will only be executed if the ‘Value’ of the field will be exactly as mentioned in the filter.

     

    For eg, if you have the following filter applied on a field from the trigger -

    exactly matches

    Then, if your incoming field value for the currency field says GBP, it won’t meet the filter condition. And hence, the filter won’t be triggered.

  2. Does not exactly match

     

    This means that the next step will only be executed if the ‘Value’ of the field is not the same as the value mentioned in the filter.

     

    For eg, if you have the following filter applied on a field from the trigger -

    does not exactly match

    Then, if your incoming field value for the currency field says USD, it won’t meet the filter condition. And hence, the filter won’t be triggered.

    However, if it says GBP, the trigger will be fired and the automation will be executed.

  3. Exists

     

    This means that the next step will only be executed if the ‘specified field’ contains a ‘value’

     

    For eg, if you have a ‘search contact using email’ step and then you applied the following filter on the ID field from the ‘search step’ -

    exists

    Then, the next action will only be executed if the ‘ID’ in the search step is found .i.e the particular email address exists in that app in which the search was performed.

  4. Does not exists

     

    This means that the next step will only be executed if the ‘specified field’ does not contain any ‘value’

     

    For eg, if you have a ‘search contact using email’ step and then you applied the following filter on the ID field from the ‘search step’ -

    does not exist

    Then, the next action will only be executed if the ‘ID’ in the search step is NOT found .i.e the particular email address does not exist in that app in which the search was performed.

  5. Contains

     

    This means that the next step will only be executed if the ‘specified field’ contains a ‘particular value’

     

    For eg, if you have the following filter applied on a field from the trigger -

    contains

    Then, the automation will be executed only if the ‘address’ field contains the words ‘new york’, irrespective of uppercase or lower case.

  6. Does not contain

     

    This means that the next step will only be executed if the ‘specified field’ does not contain a ‘particular value’

     

    For eg, if you have the following filter applied on a field from the trigger -

    does not contain

    Then, the automation will only be executed if the ‘comments’ field does not contain the words ‘not satisfied’, irrespective of uppercase or lower case.

  7. Starts with

     

    This means that the next step will only be executed if the ‘value’ of the specified field starts with a ‘particular value’.

     

    For eg, if you have the following filter applied on a field from the form (trigger) -

    starts with

    Then, the automation will be executed only if the ‘answer’ of the particular question starts with ‘yes’, irrespective of uppercase or lower case.

  8. Does not start with

     

    This means that the next step will only be executed if the ‘value’ of the specified field does NOT start with a ‘particular value’.

     

    For eg, if you have the following filter applied on a field from the form (trigger) -

    does not start with

    Then, the automation will be executed only if the ‘answer’ of the particular question does NOT start with ‘no’, irrespective of uppercase or lower case.

  9. Greater than

     

    This means that the next step will only be executed if the ‘numeric value’ of the specified field is greater than the ‘specified value’.

     

    For eg, if you have the following filter applied on a field for Quantity -

    greater than

    Then, the automation will be executed only if the ‘quantity’ > 4.

  10. Less than

     

    This means that the next step will only be executed if the ‘numeric value’ of the specified field is less than the ‘specified value’.

     

    For eg, if you have the following filter applied on a field for Quantity -

    less than

    Then, the automation will be executed only if the ‘quantity’ < 10.

  11. Ends with

     

    This means that the next step will only be executed if the ‘value’ of the specified field ends with a ‘particular value’.

     

    For eg, if you have applied a filter on the ‘time’ field of a scheduling app, such that only if the time is in ‘am’, will it be assigned to ‘X’ person -

    ends with

    Then, only when the ‘field value’ of the time will show ‘am’, will this automation be executed.

  12. Does not end with

     

    This means that the next step will only be executed if the ‘value’ of the specified field does NOT end with a ‘particular value’.

     

    For eg, if you have applied a filter on the ‘time’ field of a scheduling app, such that only if the time is NOT in ‘am’, will it be assigned to ‘X’ person

    does not end with

    Then, only when the ‘field value’ of the time will NOT show ‘am’, will this automation be executed.

Branching

Branching can be described as creating ‘If.. Else’ strings for an automation. Like defining various scenarios for the same automation.

 

Let’s say you want to create an automation where:

 

When a deal is updated in CompanyHub:

  • If deal stage is updated to proposal

    • Create a task in Todoist
  • Else

    • If deal stage is updated to won

      • Create a proposal in Nusii

    • Else

      • Create a subscriber in MailerLite

Create automations within a single app

You can create integrations not only with other apps, but also within the same app. It would be like automating a process within the app.

 

To put it in simple words, when step 1 takes place, it would lead to step 2, forming an automated process thereby.

 

Steps to create the automation

 

  1. Choose the same app twice instead of two different apps
  2. Select the ‘when’ and ‘then’ conditions
  3. Map fields, if required
  4. Add account
  5. Modify conditions and actions, if required
  6. Test and Go live
Facing an issue with connecting your account?

If you are facing problem with connecting your accounts with Integrately, there could be several reasons for it:

  • Your subscription plan does not support disclosure of API credentials
  • Incorrect API credentials
  • Changes in password of the app(s)
  • Incorrectly sourcing auto-saved login credentials in API field(s)

You need to resolve any such issue(s) to facilitate connection of your accounts with Integrately.

Facing issues when testing your automation?

If there is some in your automation, you will receive an error notification at the top while testing your automation. In that case, you won’t be able to proceed unless you have fixed the problem.

 

Now there could be a few reasons for such errors. These include:

  • Compulsory (*) field left unmapped
  • Mapped field is empty at the source
  • The test record does not exist any more
Is your Automation failing?

You have done everything right up till now, but still not able to see the results of the automation? Well, let's look at some of the most popular reasons due to which the automation may be failing:

  • Incorrect mapping of fields
  • Data being sent to app is not in proper format
  • Required field is empty
  • Authentication failed - Need to authenticate again
  • App is down

So how to recognize the error in the automation? For that, you need to check the ‘History’ of your automation. It will show an error message along with the field that caused the error.

For added convenience, Integrately will send you an email for the same stating the issue.