← All use cases

Contact requests straight into your CRM

Contact via the website → email goes out, records are created in SuiteCRM, message to the partner team.

Contact form submittedTally
  • Create account, contact, caseSuiteCRM
  • Send confirmation emailEmail account
  • Notify sales teamMatrix *

This automation runs for the konnek team. If you fill in the partner form on our website, this is the journey your message takes: an email goes out, your request is saved in SuiteCRM, and the team gets a message in Matrix that you have contacted us.

The konnektor on konnek's visual canvas. At the top, three triggers: "Manual input" and two Tally forms. Below them, one after another, the steps SuiteCRM_slug marked JS, konnek_Email_Aktor, suiteCRM getToken marked POST, three times suiteCRM Create any Module marked POST, Matrix getToken marked POST and Matrix send Message marked PUT.
Its triggers and steps: the konnektor behind the contact requests.

The KonnektorKonnektors are your automations: aktors that run one after another.More on the product page has two Tally forms as its TriggerA trigger starts a process. That can be you, the agent or an external webhook.More on the product page . Both pass on the data entered. As always, this process can also be started by hand, with real data or test data.

JavaScript creates an ID

The first step is a AktorThe aktor is the smallest step of a process. It calls a tool over HTTP, sends an email or runs your own JavaScript.More on the product page . It takes the company’s and the person’s name and builds an ID for each from them. In our case, a company ID only consists of letters, digits and hyphens.

Why do we do this? It provides us with a unique ID we control and which can be reused in different systems, as a unique identifier of the person and the company. This is the basis for every good automation.

Also, it’s a nice example of the multi-purpose tool JavaScript: almost anything can be built. And users don’t need to write it themselves. Our AgentThe agent reads your tools' documentation and builds aktors and konnektors from it.More on the product page creates JavaScript for them; all they have to do is say what they want.

Sending an email

The AktorThe aktor is the smallest step of a process. It calls a tool over HTTP, sends an email or runs your own JavaScript.More on the product page sends an email with the details. It goes out first, before anything is saved in the CRM.

Creating records in SuiteCRM

Next, a token for SuiteCRM is requested. Once that works, a AktorThe aktor is the smallest step of a process. It calls a tool over HTTP, sends an email or runs your own JavaScript.More on the product page creates three kinds of records (modules), one after another. A record is, for instance, a company account. When setting up the step, users decide which module to create. In this use case it’s these three:

  • Account
  • Contact
  • Case

Each step passes the ID of the record it just created to the next one, so the three records end up linked.

The settings of the SuiteCRM aktor that creates a case. Its inputs are the SuiteCRM address, the token from the sign-in and the attributes name, contact_id, description and contact_created_by_id, filled with values from the form and from the step before. moduleType is set to Cases.
Creating the case: placeholders fill fields dynamically.

Tell the team in Matrix

After retrieving a token, a message is posted in the partner channel, informing the relevant team members of the new partner request.

The Matrix sign-in aktor. Its inputs are the Matrix address, a user and a password. User and password are not shown as values but as the names of two secrets. The output is the Matrix token.
Secrets stay masked: the aktor only refers to them by name.

Tools in this flow

Swap any of them.

  • Tally Belgium
  • SuiteCRM United Kingdom
  • Matrix * Open Standard

Your process not listed?

Happy to show you how konnek can automate your specific workflow.

Talk to us