Fluent Support Developers

fluent_support_before_assigning_role

This action is triggered before assigning a role to a user.

Parameters

'$user' (array) User data

Usage

php

add_action('fluent_support/before_assigning_role', function ($user) {
     // ...do something
}, 10, 1);

Reference

do_action('fluent_support/before_assigning_role', $user)

This action is located in
fluent-support/app/Modules/Auth/AuthService.php

fluent_support_after_assigning_role

This action is triggered after assigning a role to a user.

Parameters

'$user' (array) User data

Usage

php

add_action('fluent_support/after_assigning_role', function ($user) {
     // ...do something
}, 10, 1);

Reference

do_action('fluent_support/after_assigning_role', $user)

This action is located in
fluent-support/app/Modules/Auth/AuthService.php

fluent_support_attachment_uploaded_as_temp

This action is triggered when attachment uploaded as temporary

Parameters

'$attachment' (object) Attachment data
'ticketId' (integer) Ticket ID

Usage

php

add_action('fluent_support/attachment_uploaded_as_temp', function ($attachment, $ticketId) {
     // ...do something
}, 10, 2);

Reference

do_action('fluent_support/attachment_uploaded_as_temp', $attachment, $ticketId)

This action is located in
fluent-support/app/Http/Controllers/UploaderController.php,
fluent-support/app/Modules/MCP/Support/AttachmentStager.php (attachments staged by MCP tools)

fluent_support_workflow_triggered

This action is triggered after a workflow is executed for a ticket.

Parameters

'$workflow' (object) Workflow object
'$ticket' (object) Ticket object
'$actor' (object) Customer or agent who triggered the workflow
'$context' (array) Additional workflow context data

Usage

php

add_action('fluent_support/workflow_triggered', function ($workflow, $ticket, $actor, $context) {
     // ...do something
}, 10, 4);

Reference

do_action('fluent_support/workflow_triggered', $workflow, $ticket, $actor, $context)

This action is located in
fluent-support-pro/app/Modules/Workflows/Runner.php,
fluent-support-pro/app/Modules/Workflows/WorkflowController.php

fluent_support_after_creating_any_response

This action is triggered after creating any response.

Parameters

'$createdResponse' (object) Response data
'$ticket' (object) Ticket data
'$person' (object) Person data

Usage

php

add_action('fluent_support/' . $conversationType . '_added_by_' . $person->person_type,
function($createdResponse, $ticket, $person) {
   // Do your stuff here
}, 20, 3);

Note: $conversationType is a dynamically assigned conversation type (some hooks use it as $convoType). Here, $person->person_type contain the type of person, whether it be an agent, user, etc.

Published drafts: fluent_support/response_added_by_agent also fires when a draft reply is published, either from the admin "Approve" action or the MCP publish-draft-reply tool. In that case $person is the agent who wrote the draft, not the agent who approved it (it falls back to the approver only when the draft has no author). The draft is already saved as a response when the action fires.

Reference

do_action('fluent_support/' . $convoType . '_added_by_' . $person->person_type, $createdResponse, $ticket, $person)

do_action('fluent_support/response_added_by_' . $sender->person_type, $response, $ticket, $sender) (draft publish)

This action is located in
fluent-support/app/Services/Tickets/ResponseService.php (fireResponseHooks() and publishDraft())

fluent_support_before_delete_email_box

This action is triggered before deleting a mailbox.

Parameters

'$box' (object) Mailbox data
'$fallbackBox' (object) Fallback mailbox data

Usage

php

add_action('fluent_support/before_delete_email_box', function ($box, $fallbackBox) {
     // ...do something
}, 10, 2);

Reference

do_action('fluent_support/before_delete_email_box', $box, $fallbackBox)

This action is located in
fluent-support/app/Http/Controllers/MailBoxController.php

fluent_support_mailbox_deleted

This action is triggered after deleting a mailbox.

Parameters

'$mailBoxId' (integer) Mailbox ID
'$fallbackBox' (object) Fallback mailbox data

Usage

php

add_action('fluent_support/mailbox_deleted', function ($mailBoxId, $fallbackBox) {
     // ...do something
}, 10, 2);

Reference

do_action('fluent_support/mailbox_deleted', $mailBoxId, $fallbackBox)

This action is located in
fluent-support/app/Http/Controllers/MailBoxController.php

fluent_support_telegram_payload_error

This action is triggered after a Telegram payload error.

Parameters

'$responseData' (array) Telegram response data
'$payload' (array) Telegram payload data

Usage

php

add_action('fluent_support/telegram_payload_error', function ($responseData, $payload) {
     // ...do something
}, 10, 2);

Reference

do_action('fluent_support/telegram_payload_error', $responseData, $payload)

This action is located in
fluent-support-pro/app/Modules/Chat/ChatController.php

fluent_support_slack_signature_verification_failed

This action is triggered when Slack webhook signature verification fails.

Parameters

'$reason' (string) Verification failure reason

Usage

php

add_action('fluent_support/slack_signature_verification_failed', function ($reason) {
     // ...do something
}, 10, 1);

Reference

do_action('fluent_support/slack_signature_verification_failed', $reason)

This action is located in
fluent-support-pro/app/Modules/Chat/Slack.php

fluent_support_delete_remote_attachment_by_driver

This action is triggered when Fluent Support deletes the remote copy of an attachment. Deletes run in the background (Action Scheduler and the hourly cron), after the ticket or reply is gone.

Parameters

'$attachment' (object) attachment data
'$ticketID' (integer|null) Ticket ID the attachment belonged to, or null when it was not on a ticket

Usage

php

add_action('fluent_support/delete_remote_attachment_' . $attachment->driver, function ($attachment,$ticketID) {
     // ...do something
}, 10, 2);

Note: $attachment->driver is the storage driver slug stored on the attachment, such as amazon_s3 or dropbox.

Since 2.4.7: this hook fires only for a storage driver that is not registered through the fluent_support/storage_drivers filter. Fluent Support Pro 2.4.7 registers its drivers, so they no longer go through this hook. New drivers should implement StorageDriverInterface instead.

Reference

do_action('fluent_support/delete_remote_attachment_' . $attachment->driver, $attachment, $attachment->ticket_id)

This action is located in
fluent-support/app/Services/Storage/StorageManager.php

fluent_support_verify_dropbox_code

This action is triggered to handle Dropbox authorization.

Parameters

'$code' (string) Dropbox verification code

Usage

php

add_action('fluent_support_pro/verify_dropbox_code', function ($code) {
     // ...do something
}, 10, 1);

Reference

do_action('fluent_support_pro/verify_dropbox_code', $code)

This action is located in
fluent-support-pro/app/Http/Controllers/AuthorizeController.php

fluent_support_run_action_from_any_saved_action

This action is triggered when an action runs.

Parameters

'$action' (string) Action name
'$workflow' (object) Workflow data
'$ticket' (object) Ticket data

Usage

php

add_action('fluent_support/run_action_' . $action->action_name, function ($action, $workflow, $ticket) {
     // ...do something
}, 10, 3);

Note: $action->action_name represents the type of action.

Reference

do_action('fluent_support/run_action_' . $action->action_name, $action, $this->workflow, $this->ticket)

This action is located in
fluent-support-pro/app/Services/Workflow/ActionRunner.php

fluent_support_ai_response_success

This action is triggered after an AI provider successfully generates a response. Use it to log usage, enforce limits, or record token consumption per agent or ticket.

Parameters

'$ticketId' (integer) ID of the ticket for which the response was generated
'$prompt' (string) The prompt sent to the AI provider
'$tokens' (integer) Number of tokens consumed by the request
'$providerName' (string) The active provider name, e.g. 'openai', 'gemini', 'anthropic', 'FluentBot'

Usage

php

add_action('fluent_support/ai_response_success', function ($ticketId, $prompt, $tokens, $providerName) {
     // log token usage per provider
}, 10, 4);

Reference

do_action('fluent_support/ai_response_success', $ticketId, $prompt, $tokens, $providerName)

This action is located in
fluent-support/app/Services/Integrations/AI/BaseAIProvider.php,
fluent-support/app/Services/Integrations/FluentBot/FluentBotAPI.php

fluent_support_mcp_loaded

This action is triggered after the MCP module has registered all its tools and is fully initialised. Use it to register additional tools or modify MCP state after the default toolkit is in place.

Parameters

None.

Usage

php

add_action('fluent_support/mcp_loaded', function () {
     // MCP is ready — register extra tools or modify state
}, 10, 0);

Reference

do_action('fluent_support/mcp_loaded')

This action is located in
fluent-support/app/Modules/MCP/MCPInit.php

fluent_support_mcp_tool_exception

This action is triggered when an MCP tool's execute callback throws an exception during a tool call, in both Core and Pro-registered tools. Use it to log or alert on runtime failures without exposing exception details to the AI client.

Parameters

'$context' (array) Exception context — ['exception' => Throwable, 'tool' => string, 'params' => array]

Usage

php

add_action('fluent_support/mcp_tool_exception', function ($context) {
     // log $context['exception'], $context['tool'], $context['params']
}, 10, 1);

Reference

do_action('fluent_support/mcp_tool_exception', ['exception' => $e, 'tool' => $toolName, 'params' => $params])

This action is located in
fluent-support/app/Modules/MCP/AbilitiesRegistrar.php,
fluent-support-pro/app/Modules/MCP/AbilitiesRegistrar.php

fluent_support_tickets_query_by_permission_ref

This action is triggered to let listeners scope a tickets query by the current agent's permissions before it runs. It receives the query builder by reference — mutate it directly rather than returning a value.

Parameters

'$ticketsQuery' (object) Ticket query builder, passed by reference
'$userId' (integer|boolean) User ID to scope by, or false to use the current user

Usage

php

add_action('fluent_support/tickets_query_by_permission_ref', function (&$ticketsQuery, $userId) {
     // mutate $ticketsQuery directly
}, 10, 2);

Note: Registered internally by PermissionFilterManager::filterAgentTickets() to scope the query to tickets the current agent can access. It's fired from ticket listing, notification queries, and several MCP tool query paths.

Reference

do_action_ref_array('fluent_support/tickets_query_by_permission_ref', [&$ticketsQuery, $userId])

This action is located in
fluent-support/app/Modules/MCP/Tools/CustomerTools.php,
fluent-support/app/Modules/MCP/Tools/ManagementTools.php,
fluent-support/app/Services/Tickets/AgentTicketAccess.php,
fluent-support-pro/app/Modules/Workflows/WorkflowController.php

fluent_support_customer_portal_tickets_query

This action is triggered to let listeners modify the customer's own ticket list query in the Customer Portal before it runs.

Parameters

'$ticketsQuery' (object) Ticket query builder, passed by reference
'$customer' (object) The customer viewing their ticket list
'$request' (object) The current request

Usage

php

add_action('fluent_support/customer_portal/tickets_query', function (&$ticketsQuery, $customer, $request) {
     // mutate $ticketsQuery directly
}, 10, 3);

Reference

do_action_ref_array('fluent_support/customer_portal/tickets_query', [&$ticketsQuery, $customer, $request])

This action is located in
fluent-support/app/Modules/CustomerPortal/PortalController.php

fluent_support_finalize_file_upload_by_driver

This action is triggered after an attachment's local file is finalized on a ticket, letting a remote storage driver push it off-server.

Parameters

'$attachment' (object) Attachment record, passed by reference
'$ticketId' (integer) Ticket ID the attachment belongs to

Usage

php

add_action('fluent_support/finalize_file_upload_amazon_s3', function (&$attachment, $ticketId) {
     // upload to S3 and update $attachment with the remote path/url
}, 10, 2);

Note: {driver} is the active storage driver slug.

Reference

do_action_ref_array('fluent_support/finalize_file_upload_' . $key, [&$attachment, $ticketId])

This action is located in
fluent-support/app/Services/Storage/StorageManager.php (finalize()),
fluent-support-pro/app/Services/Integrations/FluentEmailPiping/ByMailHandler.php (only with Fluent Support older than 2.4.7)

fluent_support_attachment_uploaded_as_temp_by_driver

This action is triggered after an attachment is uploaded as a temporary file for a specific storage driver, in addition to the generic `fluent_support/attachment_uploaded_as_temp` action above.

Parameters

'$attachment' (object) Attachment record, passed by reference
'$ticketId' (integer) Ticket ID

Usage

php

add_action('fluent_support/attachment_uploaded_as_temp_dropbox', function (&$attachment, $ticketId) {
     // ...do something
}, 10, 2);

Note: {driver} is the active storage driver slug.

Reference

do_action_ref_array('fluent_support/attachment_uploaded_as_temp_' . $key, [&$attachment, $ticketId])

This action is located in
fluent-support/app/Services/Storage/StorageManager.php (afterTempUpload())

fluent_support_update_verification_failed

This action is triggered when a plugin update package fails signature/source verification and the update is blocked.

Parameters

'$slug' (string) The plugin slug being updated
'$code' (string) Machine-readable rejection code
'$message' (string) Human-readable rejection message shown to the user

Usage

php

add_action('fluent_support/update_verification_failed', function ($slug, $code, $message) {
     // log or alert on a blocked update
}, 10, 3);

Reference

do_action('fluent_support/update_verification_failed', $this->slug, $code, $message)

This action is located in
fluent-support-pro/app/Services/PluginManager/UpdateVerifier.php

fluent_support_verify_google_code

This action is triggered to handle Google Drive authorization.

Parameters

'$code' (string) Google OAuth verification code

Usage

php

add_action('fluent_support_pro/verify_google_code', function ($code) {
     // ...do something
}, 10, 1);

Reference

do_action('fluent_support_pro/verify_google_code', $code)

This action is located in
fluent-support-pro/app/Http/Controllers/AuthorizeController.php

fluent_support_main_tickets_query

This action is triggered after the admin ticket list query has been built (filters, search and sort applied) and before it is paginated. Use it to add your own constraints to the agent ticket list. The query builder is passed by reference, so change it in place instead of returning a value.

It also fires inside the internal notifications query, where it scopes the ticket relation of each notification. In that call $args is an empty array.

Check the name for your version. Fluent Support 2.4.5 and earlier fire this only with a backslash: fluent_support\main_tickets_query. Later versions fire the backslash name and then the slash name. Use the backslash name to support every version, and listen on only one of the two, or your callback runs twice.

Core uses the backslash name internally (PermissionFilterManager::filterAgentTicketsByMailboxes()) to apply agent mailbox restrictions.

Parameters

'$ticketsQuery' (object) Ticket query builder, passed by reference
'$args' (array) The query arguments: with, filter_type (simple or advanced), filters_groups, filters_groups_raw, sort_by, sort_type, limit, offset, simple_filters, customer_id, search. Empty array when fired from the notifications query

Usage

php

add_action('fluent_support/main_tickets_query', function ($ticketsQuery, $args) {
    // Hide tickets from one product in the agent ticket list
    $ticketsQuery->where('product_id', '!=', 12);
}, 10, 2);

Reference

do_action_ref_array('fluent_support/main_tickets_query', [&$ticketsQuery, $this->args])

This action is located in
fluent-support/app/Services/Tickets/TicketQuery.php

fluent_support_tickets_filter_by_provider

This action is triggered once for each filter provider in each group of the advanced ticket filter. The dynamic part `{provider}` is the first element of the filter's `source` (for example `tickets`, `customer` or `agent`). Groups are OR-ed together; providers inside a group are AND-ed. The query builder is passed by reference, so add your `where` clauses to it in place.

Fluent Support Pro registers the tickets, customer and agent providers (on the backslash names). Register your own provider name to support a custom filter source.

Check the name for your version. Fluent Support 2.4.5 and earlier fire this only with a backslash: fluent_support\tickets_filter_{provider}. Later versions fire the backslash name and then the slash name. Use the backslash name to support every version, and listen on only one of the two, or your callback runs twice.

Parameters

'$query' (object) Query builder for the current filter group, passed by reference
'$items' (array) The filter items for this provider in this group. Each item has property (second element of source), operator and value

Usage

php

add_action('fluent_support/tickets_filter_my_source', function ($query, $items) {
    foreach ($items as $item) {
        if ($item['property'] === 'priority' && $item['operator'] === '=') {
            $query->where('client_priority', sanitize_text_field($item['value']));
        }
    }
}, 10, 2);

Reference

do_action_ref_array('fluent_support/tickets_filter_' . $providerName, [&$q, $items])

This action is located in
fluent-support/app/Services/TicketQueryService.php

fluent_support_customer_email_verified_change

This action is triggered after a customer's contact email moves to a new, proven address. Before it fires, Fluent Support rotates the hash of every ticket the customer owns (so signed links sent to the old inbox stop working) and logs a `fluent_support/customer_email_changed` activity.

It fires when the linked WordPress account's email change was confirmed by WordPress (verified) or made by someone else who can edit that account (administrator), when the customer confirms a support address claim from the portal (claimed), and when an agent changes the customer's email from the admin (agent).

Parameters

'$customer' (object) The customer model, already saved with the new email
'$previousEmail' (string) The email the customer had before the change
'$reason' (string) How the change was proven: verified, administrator, claimed or agent

Usage

php

add_action('fluent_support/customer_email_verified_change', function ($customer, $previousEmail, $reason) {
    // Keep an external CRM in sync
    my_crm_update_email($previousEmail, $customer->email);
}, 10, 3);

Reference

do_action('fluent_support/customer_email_verified_change', $customer, $previousEmail, $reason)

This action is located in
fluent-support/app/Services/ProfileInfoService.php

fluent_support_merging_customer_records

This action is triggered while one customer record is folded into another during a support email claim. When a customer confirms a new address from the portal, any unlinked customer record already holding that address is absorbed into theirs.

It fires after core has moved the source record's tickets, conversations, attachments, activities, notifications and person meta, and before the source record is deleted. The source is deleted only if nothing still points at it, so move any rows you keep keyed by the customer's person ID here. Fluent Support Pro uses this hook to move time tracking entries.

Parameters

'$source' (object) The customer record being absorbed (removed afterwards)
'$target' (object) The customer record it is merged into

Usage

php

add_action('fluent_support/merging_customer_records', function ($source, $target) {
    global $wpdb;
    $wpdb->update(
        $wpdb->prefix . 'my_customer_notes',
        ['customer_id' => $target->id],
        ['customer_id' => $source->id]
    );
}, 10, 2);

Reference

do_action('fluent_support/merging_customer_records', $source, $target)

This action is located in
fluent-support/app/Services/EmailClaimService.php,
fluent-support-pro/app/Hooks/actions.php (listener)

fluent_support_system_tools_database_repair

This action is triggered when an admin runs **Repair** on the System Tools > Database Health page, after the core migrations re-run (since 2.4.5). Add-ons that register tables through `fluent_support/system_tools_tables` should create them here.

Parameters

None

Usage

php

add_action('fluent_support/system_tools_database_repair', function () {
     // ...create your add-on tables
}, 10, 0);

Reference

do_action('fluent_support/system_tools_database_repair')

This action is located in
fluent-support/app/Modules/SystemTools/DatabaseHealth.php