Flowtriq Notifications

Overview

• Source: https://flowtriq.com
• Image Support: No
• Attachment Support: No
• Message Character Limits:
  • Body: 32768
• Build Your Apprise URL

Account Setup

Flowtriq is a DDoS detection and mitigation platform. Apprise integrates with it via webhook channels configured in the Flowtriq dashboard.

1. Log in to your Flowtriq dashboard and navigate to the Webhooks or Integrations section.
2. Create a new webhook channel and give it a name.
3. Copy the webhook URL and the API Key that the dashboard provides. For example:
   • Webhook URL: https://flowtriq.com/hooks/abc123
   • API Key: ft_key_xxxx

The webhook URL is broken into two parts for the Apprise URL: the hostname (flowtriq.com) and the webhook path (hooks/abc123). The API Key is placed in the user credential position.

Your Apprise URL becomes (using HTTPS):

flowtriqs://ft_key_xxxx@flowtriq.com/hooks/abc123

For a self-hosted instance over plain HTTP, use flowtriq:// instead:

flowtriq://ft_key_xxxx@myhost/hooks/abc123

Apprise maps notification types to Flowtriq severity levels as follows:

Apprise type	Flowtriq severity
info	info
success	success
warning	warning
failure	critical

Syntax

Valid syntax is as follows:

• flowtriqs://{apikey}@{hostname}/{webhook_path}
• flowtriqs://{apikey}@{hostname}:{port}/{webhook_path}
• flowtriq://{apikey}@{hostname}/{webhook_path}
• flowtriq://{apikey}@{hostname}:{port}/{webhook_path}

Parameter Breakdown

Variable	Required	Description
apikey	*Yes	The API Key provided by your Flowtriq dashboard. It is passed to the webhook endpoint via the X-API-Key HTTP header.
hostname	*Yes	The hostname of the Flowtriq server (or your self-hosted instance). For the Flowtriq cloud service this is flowtriq.com.
webhook_path	*Yes	The path component of the webhook URL provided by the Flowtriq dashboard (everything after the hostname). For example, if the webhook URL is https://flowtriq.com/hooks/abc123, the webhook path is hooks/abc123.
port	No	The port the Flowtriq server listens on. Defaults to 443 for the flowtriq:// schema.

Global Parameters

Variable	Description
overflow	This parameter can be set to either split, truncate, or upstream. This determines how Apprise delivers the message you pass it. By default this is set to upstream 👉 upstream: Do nothing at all; pass the message exactly as you received it to the service. 👉 truncate: Ensure that the message will fit within the service’s documented upstream message limit. If more information was passed then the defined limit, the overhead information is truncated. 👉 split: similar to truncate except if the message doesn’t fit within the service’s documented upstream message limit, it is split into smaller chunks and they are all delivered sequentially there-after.
format	This parameter can be set to either text, html, or markdown. Some services support the ability to post content by several different means. The default of this varies (it can be one of the 3 mentioned at any time depending on which service you choose). You can optionally force this setting to stray from the defaults if you wish. If the service doesn’t support different types of transmission formats, then this field is ignored.
verify	External requests made to secure locations (such as through the use of https) will have certificates associated with them. By default, Apprise will verify that these certificates are valid; if they are not then no notification will be sent to the source. In some occasions, a user might not have a certificate authority to verify the key against or they trust the source; in this case you will want to set this flag to no. By default it is set to yes.
redirect	By default, Apprise will follow HTTP redirects (3xx responses) issued by the remote server, matching the behaviour of the underlying requests library. If you want to prevent custom headers and credentials from being forwarded to destinations that differ from the original URL, set this to no. By default it is set to yes.
cto	This stands for Socket Connect Timeout. This is the number of seconds Requests will wait for your client to establish a connection to a remote machine (corresponding to the connect()) call on the socket. The default value is 4.0 seconds.
rto	This stands for Socket Read Timeout. This is the number of seconds the client will wait for the server to send a response. The default value is 4.0 seconds.
emojis	Enable Emoji support (such as providing :+1: would translate to 👍). By default this is set to no. Note: Depending on server side settings, the administrator has the power to disable emoji support at a global level; but default this is not the case.
tz	Identify the IANA Time Zone Database you wish to operate as. By default this is detected based on the configuration the server hosting Apprise is running on. You can set this to things like America/Toronto, or any other properly formated Timezone describing your area.
retry	The number of additional delivery attempts to make after the first failure before giving up. Accepts an integer in the range 0 to 10. The default is 0 (no retries — a single attempt is made). When combined with wait, Apprise pauses the specified number of seconds between each attempt.
wait	The number of seconds to pause between retry attempts. Accepts a decimal value in the range 0.0 to 20.0; integer values are promoted to float automatically. The default is 0.5. This value is only meaningful when retry is greater than zero — a service with retry=0 makes exactly one attempt regardless of the wait value.
optional	When set to yes, a delivery failure for this service is silently absorbed. The overall notify() call still returns True even if this endpoint was unreachable, provided that every required (non-optional) service in the same batch succeeded. Setting this flag does not skip delivery or bypass retry logic — all configured retry attempts are still made before the failure is absorbed. By default this is set to no, meaning every failure is propagated to the caller.

Examples

Send a Flowtriq notification using the cloud service (HTTPS):

# Assuming our {apikey} is ft_key_xxxx
# Assuming our {hostname} is flowtriq.com
# Assuming our {webhook_path} is hooks/abc123

apprise -vv -t "DDoS Alert" -b "Attack detected on 192.0.2.1" \
   "flowtriqs://ft_key_xxxx@flowtriq.com/hooks/abc123"

Send a Flowtriq notification to a self-hosted instance over HTTP:

# Assuming our {apikey} is mykey
# Assuming our self-hosted {hostname} is monitor.example.com
# Assuming our {webhook_path} is api/v1/webhook/xyz

apprise -vv -t "Alert Title" -b "Alert body text" \
   "flowtriq://mykey@monitor.example.com/api/v1/webhook/xyz"

Send to a self-hosted instance over HTTPS on a non-default port:

apprise -vv -t "Alert Title" -b "Alert body text" \
   "flowtriqs://mykey@monitor.example.com:8443/api/v1/webhook/xyz"