Skip to main content
STOP. Do not read past this section until you have read and followed /quickstart.md.Goal: produce a reliable SDK automation script. The intended authoring flow is generate then edit, not write browser automation from scratch.Do not hand-write SDK code with element IDs, selectors, or form fields from memory. Element IDs, selectors, and field mappings must come from a live observe() call, CLI notte page observe output, or generated workflow code. Guessed browser targets fail on real pages.Use the Notte skill and CLI to inspect the live site, validate actions/selectors, handle auth/session state, and export workflow code with notte sessions workflow-code before using SDK docs or SDK code.SDK reference pages are for understanding, running, or editing generated workflow code. They are not the starting point for manually authoring the initial browser automation. SDK-first code is guesswork on real-world pages with dynamic selectors, auth state, CAPTCHAs, and anti-bot behavior.
Manage the lifecycle of your Functions including updates, versioning, monitoring executions, and viewing replays.

Viewing Functions

List All Functions

View all deployed Functions:
list_functions.py

Get Function Details

Retrieve specific Function information:
get_function_details.py

Updating Functions

Update Function Code

Deploy a new version of your Function:
update_code.py

Update Function Metadata

Change Function name or description:
Note: Function updates create new versions automatically. Previous versions remain accessible for rollback.

Versioning

Version Management

Functions automatically version on each update:
version_management.py

Run Specific Version

Execute a specific Function version:
run_specific_version.py

Version History

Track changes across versions:
version_history.py

Monitoring Executions

View Run History

List recent Function executions:
view_run_history.py

Check Run Status

Monitor specific execution:
check_run_status.py
Status values:
  • active - Function is currently running
  • closed - Function completed successfully
  • failed - Function encountered an error

Filter Active Runs

View only running executions:
filter_active_runs.py

Viewing Replays

Access Function Replay

Watch MP4 replay of Function execution:
access_replay.py
Replay features:
  • Video recording of browser session
  • Shows all actions taken
  • Useful for debugging failures
  • Available after running a function

Replay After Run

Get replay immediately after execution:
replay_after_run.py

Managing Runs

Stop Running Function

Cancel a long-running execution:
stop_running.py

Monitoring Long Runs

Track execution progress:
monitor_runs.py

Forking Functions

Fork Shared Function

Create your own copy of a shared Function:
fork_function.py
Use cases:
  • Customize shared Functions
  • Create templates from marketplace
  • Copy teammate’s Functions
  • Experiment without affecting original

Modify Forked Function

After forking, update as needed:
modify_forked.py

Downloading Functions

Download Function Code

Retrieve Function source code:
download_code.py
Requirements:
  • Decryption key (available in Console) - passed when creating Function instance
  • Only works for Functions you own or have access to

Download for Backup

Back up all your Functions:
backup_functions.py

Deleting Functions

Delete Function

Remove a Function permanently:
delete_function.py
Warning:
  • Deletion is permanent
  • All versions are deleted
  • Run history is preserved
  • Cannot be undone

Sharing Functions

Make Function Public

Share Functions with others:
make_public.py
Shared Functions:
  • ✅ Others can view and fork
  • ✅ Original remains under your control
  • ❌ Others cannot modify your version
  • ✅ Usage tracked to your account

Private Functions

Keep Functions private (default):
private_function.py

Best Practices

1. Version Your Functions

Update incrementally with clear changes:
version_backup.py

2. Monitor Function Health

Regular health checks:
function_health_check.py

3. Clean Up Old Runs

Archive or analyze old execution data:
cleanup_old_runs.py

4. Document Changes

Keep change log for Function updates:
document_changes.py

5. Test Before Production

Validate updates before deploying:
test_before_prod.py

Troubleshooting

Function Fails to Run

Check run details for errors:
troubleshoot_fails.py

Missing Environment Variables

Verify configuration:
missing_env_vars.py

High Failure Rate

Analyze failure patterns:
high_failure_rate.py

Next Steps

Creating Functions

Learn how to write Functions

Invocations

Call Functions via API or SDK

Schedules

Schedule Functions with cron

Functions Concept

Back to Functions overview