bbdrop

Hooks & Automation

Hooks let you run external scripts or programs at key points in the gallery lifecycle. Combined with JSON key mappings, they create a pipeline where external tool output flows directly into your BBCode templates.

Hook Events

Three events are available:

Event	When It Fires
On Gallery Added	When a gallery is added to the queue
On Gallery Started	When a gallery upload begins
On Gallery Completed	When a gallery upload finishes successfully

Setting Up a Hook

Go to Settings > Hooks (or click the App Hooks button) and configure any of the three events.

Command Builder

Each hook has a command template — a command line with % variables that get replaced with gallery data at runtime:

python my_script.py "%N" "%p" --images %C

Available variables:

Variable	Description	Available
%N	Gallery name	All events
%T	Tab name	All events
%p	Gallery folder path	All events
%C	Number of images	All events
%s	Gallery size in bytes	All events
%t	Template name	All events
%z	ZIP archive path (created on demand)	All events
%e1-%e4	ext field values	All events
%c1-%c4	custom field values	All events
%g	Gallery ID	On Completed only
%j	JSON artifact path	On Completed only
%b	BBCode artifact path	On Completed only

Use %% for a literal percent sign.

The Insert % Variable dropdown and live preview help you build commands. Click Run Test Command to test with sample data before saving.

!!! tip Always wrap % variables in quotes in your command template (e.g., "%N" not %N) to handle gallery names with spaces.

Execution Mode

• Parallel — All hooks run simultaneously (default)
• Sequential — Hooks run one at a time in order

JSON Key Mappings

This is where hooks become powerful. If your external program outputs JSON to stdout, BBDrop can map specific keys back into the gallery’s ext fields.

How It Works

1. Your script prints JSON to stdout:

   {"download_url": "https://example.com/abc123", "file_id": "abc123"}
   

2. In the JSON Key Mappings section, map keys to ext fields:
   • ext1 → download_url
   • ext2 → file_id

3. BBDrop parses the JSON, extracts the values, and stores them in the gallery’s ext1 and ext2 fields.

4. Those fields are now available in your BBCode templates as #ext1# and #ext4#:

   [if ext1]Download: [url=#ext1#]Link[/url][/if]
   

Testing

When you click Run Test Command, the output panel shows:

• Left side — Parsed JSON in a table format (if valid JSON detected)
• Right side — Raw stdout/stderr output

BBDrop can auto-detect URLs, file paths, and IDs in the output and suggest mappings.

Console Options

• Show console window when executing — Display a command window while the hook runs (Windows). Useful for debugging scripts that prompt for input or show progress.

Example: Adding a File Host Link via Hook

A script that uploads an archive to a custom host and returns the link:

Command:

python upload_to_host.py "%z" --name "%N"

Script output:

{"url": "https://myhost.com/files/abc123"}

Mapping: ext1 → url

Template usage:

[if ext1]My Host: [url=#ext1#]Download[/url][/if]

The download link appears in your BBCode automatically, only when a URL was actually returned.

Example: Multi-Host Integration

Upload to both GoFile and Pixeldrain after gallery completion, then reference both links in your template.

Hook 1 — GoFile:

python hooks/muh.py gofile "%z"

Mapping: ext1 → download_link

Hook 2 — Pixeldrain:

python hooks/muh.py pixeldrain "%z"

Mapping: ext2 → download_link

Template usage:

[b]Download Links:[/b]
[url=#ext1#]GoFile[/url] | [url=#ext2#]Pixeldrain[/url]

Each hook maps its output to a different ext field, so the template can reference both links.

Troubleshooting

Hook Not Executing

1. Check that the correct event is selected (e.g., “On Gallery Completed” for post-upload hooks)
2. Verify the command path is correct — use a full path if the executable isn’t on PATH
3. Check the working directory setting (defaults to the BBDrop folder)
4. Open the log viewer (Ctrl+L) to see error messages from the hook executor

Parameters Not Substituted

1. Always quote variables in your command template — "%N" not %N
2. Fields may be empty at runtime; quoting prevents argument splitting
3. Multi-character variables like %e1 are matched before single-character ones like %e

JSON Output Not Captured

1. Enable the Capture Output checkbox for the hook
2. Verify the script outputs valid JSON to stdout (test it outside BBDrop first)
3. Check that JSON key names in the mapping match exactly what the script outputs
4. Use Run Test Command to see parsed output and verify mappings
5. Check logs for JSON parsing errors

Hook Timeout

1. Increase the timeout value (in seconds) in the hook configuration
2. For file host uploads, allow at least 300 seconds (5 minutes)
3. Slow network connections need longer timeouts — check your upload speed
4. Check logs for timeout messages

This site is open source. Improve this page.