BIG-IP F5 icon

BIG-IP F5

Interact with F5 BIG-IP via the iControl REST API

Actions38

ASM → Export Signatures

AI-generated

Summary

Starts an ASM background task on the BIG-IP that exports the current attack signature set to a named file on the device's filesystem, via POST /mgmt/tm/asm/tasks/export-signatures.

Inputs

  • Export Filename (required) — Filename on the BIG-IP filesystem to write the exported signatures to (e.g. signatures_export.xml). Sent as filename in the JSON request body.
  • Request Options — Optional node settings: batching (items per batch, default 50, and interval in ms, default 1000), ignore SSL issues, HTTP proxy URL, and timeout in ms (default 10000).

Output shape

One JSON response per input item, containing the iControl REST reply for the created export-signatures task. This is typically a task record with an ID and status.

The export runs asynchronously on the BIG-IP and the file is written on the device, not returned to n8n. Use the ASM 'Check Task Status' operation with task type 'export-signatures' and the returned task ID to confirm completion. The exact response fields are not defined in the node source. The node uses declarative routing with the host and SSL settings from the bigIpF5Api credential.

Examples

Example 1: Back up the current attack signature set before applying a signature update.

Resource: ASM; Operation: Export Signatures; Export Filename: signatures_backup.xml. Follow with Check Task Status (task type export-signatures) using the returned task ID.

Links

Discussion