Bring Ad Campaign Management
to CrewAI

1. Go to developers.facebook.com and log in.
2. Click My Apps → Create App.
3. Select Business as the app type.
4. Fill in the app name and connect it to your Business Manager.
5. Add the Marketing API product to your app.
6. Go to Settings → Basic and copy your App ID and App Secret.
7. Generate a System User Access Token in Business Manager (Business Settings → System Users → Generate Token).
8. Paste all values below.

💡 For production use, submit your app for App Review to get stable, long-lived tokens.

Yes. Meta Ads Manager unifies Facebook and Instagram advertising. Your AI agent manages campaigns across both platforms through the same API — including placements in Feed, Stories, Reels, and Messenger.

Yes. Your AI agent can create lookalike audiences from customer lists, website visitors, or app users — with configurable similarity percentages (1% being most similar, 10% broadest reach).

Track purchases, add-to-cart, initiate checkout, lead submissions, app installs, registrations, page views, and custom conversion events — with attribution windows of 1-day click, 7-day click, and 1-day view.

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.