TAQ Triggers

Try @HumanBuy @Human SubscriptionJoin @Human Community

Creating Triggers

The first block on any TAQ Canvas will be the "Add Trigger" block

Clicking on "Add Trigger" will open a modal from which you can select a Trigger type

Trigger Types

There are 4 key types of TAQ Triggers. They are mostly self-explanatory.

• System Triggers include Manual (i.e. button on a Namespace application), Interval (e.g. every 24 hours) and Timestamp (e.g. DD-MM-YYYY)

• Record Triggers involve triggering a TAQ before and after Namespace application records are created, updated or deleted (e.g. after a lead is created in the @Human CRM, the user will receive a notification)

• User Triggers involve triggering a TAQ after users are created, updated, suspended or deleted (e.g. when a user is created, send them a welcome notification)

• Agent Invoke Triggers are used when a TAQ needs to receive the output of an Agent as its triggering input. The Agent Invoke Trigger enables safe handover between the Agent and the TAQ.

• Connection Triggers refer to trigger events from third party connections (e.g. when a new branch is created in Github, update the engineering events record).

System Triggers

Manual Trigger

The Manual Trigger is the simplest to configure in the TAQ itself.

To use a Manual Trigger in a Namespace application, you will need to add an Automation block in a Page Builder.

The button can be added to any page and sized or coloured as required

Interval Trigger

As the name suggests, you may choose an interval from the dropdown list. The TAQ will run each time this interval occurs

Timestamp Trigger

Pick a specific date and time at which you require your TAQ to run

Record Triggers

After Record Create

This Trigger is one of the most popular. You need to enter both the Namespace application and the specific Module in which the Record will be created. The TAQ will start each time a record is created in this module (e.g. a new lead has been created in the Lead Module of the CRM Namespace, then prompt an agent to write a welcome email and send it the following morning at 9am)

After Record Delete

You need to enter both the Namespace application and the specific Module in which the Record will be created. The TAQ will start each time a record is created in this module.

After Record Undelete

Records at the Namespace application layer are only "soft" deleted in @Human (Hard delete is done at the database layer). This can be a useful feature e.g. if records need to be recovered in order to continue process.

After Record Update

Changes to records can often be used to trigger process e.g. a change in an employee's status might imply the need to have new system roles.

Before Record Create

This is a particularly useful Trigger for cross-checks e.g. verifying that an account does not already exist before you create a new one.

Before Record Delete

This Trigger is useful for cross-checks before removing a record e.g. are there any related outstanding actions, such as support requests, required for an account before the record is deleted.

Before Record Undelete

Can be useful in scenarios where undeletion is subject to a policy check or in scenarios where duplication checking might be necessary.

Before Record Update

Excellent for checking whether changes have already been applied or for creating conditional logic based on an existing record state.

Agent Invoked Trigger

The Agent Invoked Trigger is specifically for use when an @Human Agent needs to invoke a TAQ and pass a value to it.

The type of value expected is usually a text string, but it can also be a number or a boolean/checkbox (e.g. when the Agent needs to confirm a decision).

The TAQ to be used by the Agent is selected within the Agent Configuration interface.