Skip to content

Add event-driven triggers

Create product event actions that generate an agreement and send approval email and SMS messages when a matching application is approved.

For
Product administrators automating documents and customer communications.
Requires
Event-action permission, the three templates from the preceding quickstart, and enabled Document Generation, Email, and SMS integrations.
Available when
The product shows Event Actions and the selected application event supports the intended action type.
Before you begin
Choose a synthetic application whose currency and recipient details satisfy the condition and whose approval can be completed by an authorised user.
Expected result
Approval creates three execution entries: a generated agreement, an email with that agreement attached, and an SMS.
Quickstart point This run
Estimated time About 30 minutes, excluding provider processing time.
Starting state The product has a Loan agreement, approval email, and approval SMS; all providers are enabled.
Finish state Three enabled product event actions respond to the same approval event and their executions are visible in Execution History.

Each action runs independently. One action can complete while another fails, so the history must be read per action rather than as one combined workflow result.

Workflow

Use one event and condition

Open Administration → Products, select the lending product, and find Event Actions. For each of the three actions below, use:

  • Event Type: Approve quote. The configuration screen uses the shared term quote for a loan application.
  • Execution Condition: Currency → Equals → EUR, or replace EUR with the currency of your synthetic application.
  • Enabled: off while entering and reviewing the action, then on when all three actions are ready.

Using the same event and condition keeps the outputs aligned. An application in another currency does not create execution entries for these actions because its condition does not match.

Generate the agreement

  1. Select Add Event Action.
  2. Enter Generate approved loan agreement as the Name.
  3. Select Approve quote as Event Type and Generate document as Action Type.
  4. Under Action Settings, select Loan agreement as Template and PDF as Output Type. Confirm that Target Entity identifies the quote/application context.
  5. Add Currency → Equals → EUR under Execution Condition.
  6. Save the action. Reopen it and confirm the event, action type, template, output type, condition, and enabled state.

This action attaches the generated file to the application. It does not send the file to a recipient.

Send the email with the agreement

  1. Add another event action named Email application approval.
  2. Select Approve quote and Email notification.
  3. Under Action Settings, choose the enabled email Provider and enter the To, Subject, and Message values. Use only paths shown in the payload preview; confirm the resolved recipient and content shown beneath dynamic fields.
  4. Under Generate and Attach, select Loan agreement.
  5. Add the same Currency → Equals → EUR condition, save, and review the enabled configuration.

Generate and Attach creates a fresh agreement for this email from the approval event's application data. It is independent from the separate Generate document action, so the email does not wait for or reuse that action's file.

Send the SMS

  1. Add a third event action named SMS application approval.
  2. Select Approve quote and SMS notification.
  3. Choose the enabled SMS Provider, then enter the recipient and concise message using paths confirmed in the payload preview.
  4. Add the same Currency → Equals → EUR condition, save, and review the enabled configuration.

Observe the first matching approval

Approve a synthetic application that uses EUR and contains safe email and mobile recipients. Approval records the decision; it does not create the loan. Lend remains a separate action.

Open Administration → Event Actions → Execution History. Filter the visible entries by their time, Event Type, and Action Type. Each action moves through Scheduled, Pending, or Running before reaching Completed or Failed. Open an entry to inspect its attempts, source event, affected references, and Last Error when present.

Completed confirms that the Finsaku action finished. For email and SMS, use provider evidence when delivery or final recipient status matters. A non-matching condition creates no execution entry.

Failures and retries

Finsaku schedules up to three automatic retries after a processing failure. The Attempts value increases as the action runs again. Do not approve another application or create a duplicate event action while an entry is Scheduled, Pending, or Running.

When an entry remains Failed after retries:

  1. open it and record the Last Error, event, action type, and affected reference;
  2. check whether the provider received the request before repeating anything;
  3. correct the integration, recipient, template, or condition that caused the failure;
  4. use a new qualifying event only when the organisation's recovery procedure confirms that another document or message will not create a duplicate.

The current interface shows retry progress and attempts in Execution History; it does not provide a manual Retry button for a failed event action.

Use Event actions for all action types and Activity and audit history for investigation guidance.