How to Link Apps in a CRM: A Step-by-Step Guide Series #

In GudHub, apps can work together, share data, and perform tasks across the system. For example, one app can store customer information while another keeps track of customer visits.

In this step-by-step series, we’ll use a practical example to show you how to connect two apps in a CRM. We’ll create a separate “Visits” app, link it to the “Clients” app, and then set it up so each client’s visit history appears in their individual client record.

You can follow the guides in order, as each one builds on the previous guide and takes the setup one step further.

What This Series Covers #

1. Creating and setting up an app for tracking customer visits.
2. Connecting the apps.
3. Exchanging data between apps.
4. Displaying related information in a client record in the PRO version.

In the previous guides, we created a fully functional app for tracking customer visits. You can add new records, select a customer from the database, and record the date of each visit – no additional PRO settings are required.

The PRO settings extend this connection by allowing the visit history to be displayed automatically in the individual client record in the “Clients” app.

In other words, the “Visits” app remains fully functional without these additional settings. The PRO version simply adds a convenient way to view related information in one place, without having to switch between apps.

Now, let’s set up the visit history to appear directly in each client’s record. To do this, we’ll add a separate section to the “Clients” app where data from the “Visits” app will be displayed.

Additional PRO Settings #

Step 1 #

Open the “Clients” app and select any record. Right-click any table field to open the context menu, then select “Template Builder”. To keep the visit information separate from the client’s other details, create a new container. Click the icon and select “Add Container”. The new container will appear in the form. Drag it below the existing client information blocks so that the visit history appears after them.

Step 2 #

Now, add a table to the new container to display data from the “Visits” app.

In the “Elements Library”, find the “Table” element and drag it into the container you created. The table needs to be configured to specify which data it should display. Right-click the table and select “Field Configurator”. Enter a name for the table in “Field Name”. Next, in “Application”, select the app that will provide the table data. In our case, select “Visits”. Then, select the fields that should be displayed in the client’s record. For this example, we only need “Client” and “Date”. You can change their order if needed. Click “Apply” to save the changes. Click “Save” to finish the configuration. The data from the “Visits” app will now be displayed in the individual client record in the “Clients” app.

Step 3 #

At this stage, there is one important detail to keep in mind: if you open any client record, the table may also display visits belonging to other clients. To prevent this, add a filter to the table so that it displays only records associated with the current client.

To do this, open “Template Builder” again. Go to the “Form” tab. Then open “Field Configurator”.

Step 4 #

In the table settings, click “Add Filter”. Select “Client”. Then configure the filter conditions by selecting the following options in order:

• “Equals (or)”

• “Variable”

In the “Select Value” field, select “Current Item”. This tells the system to compare the client in each visit record with the client whose record is currently open. As a result, each client record will display only the visits associated with that client.

Click “Apply” to save the changes. Then click “Save”. The individual client records will now display only that client’s own visit history. With this, we have set up a complete connection between the “Clients” and “Visits” apps: visit data is stored in a separate app, automatically linked to the corresponding client, and displayed in that client’s individual record.