Prompt Pilot Pro 🤖🌐

📌 Introduction

🎯 What is Prompt Pilot Pro?

Prompt Pilot Pro is a powerful AI-powered browser automation Actor that executes your instructions against a real cloud browser. Describe what you want to do in plain English, and the Actor handles the rest — logging in, navigating pages, filling forms, clicking buttons, and downloading files.

Built on Browserbase (cloud browser infrastructure), it turns plain-English instructions into reliable browser automation — no scripts required.

---

🚀 Key Features

• Natural language automation — describe actions in plain English; AI handles execution
• Cloud browser sessions — runs on real Browserbase browsers with persistent context support
• File downloads — automatically retrieves files downloaded during the session
• Variable substitution — use %key% tokens for dynamic values across all steps
• Credential & OTP integration — fetch credentials and one-time passwords from external APIs at runtime
• Session reuse — persist cookies and login state across runs via contextId

---

🔍 Use Cases

• File downloads — automate file retrieval from authenticated web portals
• Authenticated workflows — log in, complete MFA, and navigate multi-step portals
• Data extraction — navigate complex websites and extract structured data
• Research automation — automate repetitive tasks across multiple websites
• Web testing — automate testing workflows with natural language

---

📥 Input

The Actor accepts a metadata object and a natural language prompt. Any key defined in metadata is automatically available as a %key% variable in the prompt.

{
  "metadata": {
    "url": "https://example.com",
    "myVar": "some value"
  },
  "prompt": "Navigate to %url% and do something with %myVar%."
}

Reserved metadata fields

A few keys in metadata have special behavior:

Field	Type	Required	Description
url	string	Yes	Starting page URL.
download	boolean	No	Retrieve files downloaded during the session. Default: true.
contextId	string	No	Persistent context ID — reuses cookies/session across runs.

All other fields are treated as user-defined variables and substituted into the prompt wherever %fieldName% appears.

Prompt

A plain-English description of what to do. All %key% tokens are replaced with values from metadata before execution.

---

✅ Example Input

{
  "metadata": {
    "url": "https://example.com",
    "download": true,
    "token": "<your-token>",
    "credential_url": "https://your-service/credentials?service=example",
    "otp_url": "https://your-service/otp?service=example",
    "startDate": "01/01/2026",
    "endDate": "01/31/2026"
  },
  "prompt": "Navigate to %url%. Retrieve the username and password from %credential_url% using token %token%, and the OTP code from %otp_url% using token %token%. Log in, then download all files from %startDate% to %endDate%."
}

---

📤 Output

When download: true, files downloaded during the session are retrieved and stored in the Actor's Key-Value Store. One Dataset record is pushed per file:

{
  "success": true,
  "originalFileName": "report.pdf",
  "sanitizedFileName": "report.pdf",
  "fileSize": 4096,
  "timestamp": "2026-02-26T10:00:00.000Z"
}

On failure:

{
  "success": false,
  "error": "No files were downloaded",
  "timestamp": "2026-02-26T10:00:00.000Z"
}

---

⚙️ How to Use

1. Log in or sign up on Apify.
2. Open the Prompt Pilot Pro Actor and go to the Input tab.
3. Switch to JSON mode and paste your input.
4. Click Start and monitor the Log tab in real time.
5. When the run completes, view downloaded files in the Key-Value Store tab and metadata records in the Dataset tab.

---

💡 Tips for Writing Prompts

• Any metadata field is a variable — add any key to metadata and reference it as %key% in the prompt.
• Be specific about actions — "Click the Submit button" is better than "Submit the form".
• Use contextId for session reuse — avoids re-logging in on every run for portals that support persistent sessions.
• Use download: false for dry runs — test navigation without triggering file retrieval.

---

🛠️ Troubleshooting

Symptom	Likely cause	Solution
401 Unauthorized on a request	Wrong or missing token	Verify token values in metadata match what your service expects
404 Not Found on OTP request	Code not yet available	Wait 30–60 seconds and re-run
MFA code rejected (wrong code)	Timing issue — code arrived late	Re-run the Actor
No files in Key-Value Store	No downloadable files found on the page	Check date range or page state
Actor fails with metadata.url is required	Input format incorrect	Ensure input has a metadata object with a url field

---

🔗 Additional Resources

• Apify Platform Documentation
• Browserbase Documentation
• Playwright Documentation