Set it up once.
Then get started.
1. Start the server
Extract the complete package. On Windows, double-click START-FUTPULSE.cmd. The first launch installs dependencies. Node.js 22 or newer is required. Keep the server window open.
2. Account and trial
Create a shop account and activate the 24-hour trial in your dashboard. Use the same account in the extension. No EA credentials are entered into the shop.
3. Install the extension
Download and extract the extension. Open Chrome or Edge extensions, enable Developer mode, and choose “Load unpacked”. Select the folder containing manifest.json. Disable older FC27 bot extensions and userscripts.
For updates, replace the files in the same extension folder, click Reload in Chrome, then reload the EA Web App tab.
Download FutPulse extension ↓4. Sign in and open the bot
Pin FutPulse to the browser toolbar. Sign in, select “Show bot”, and open Transfers in the EA Web App. Review targets and prices, test in dry-run mode, then start deliberately.
“License server unavailable”
Check whether the server window is still running. For local setup, the shop must be reachable at http://localhost:8787 on the same computer as the extension. A remote setup needs a running HTTPS server; a quick tunnel expires when stopped. The extension download from that shop is configured for its PUBLIC_ORIGIN. Use Advanced server settings only when the address changes.
“No active license”
Activate your trial or purchase an available plan in the account dashboard. Then sign in to the extension again. Shop and extension sessions are independent.
The bot is not visible
Click “Show bot” in the popup. If asked, reload the EA Web App tab. After an update, the old page may still run old code. Make sure Chrome permits the extension on www.ea.com.
Forgot password
The operator can reset passwords at /admin.html. A random admin key is generated in admin-key.txt at first startup. Automatic password reset emails are not available.
Share diagnostics
Select “Diagnostics ↓” in the bot dashboard. The export contains search settings and logs, but no EA session identifier, passwords or license token.