Manus AI: Automate structured tasks directly from CrocoClick
Integrate Manus AI into CrocoClick to create, manage and continue AI tasks directly in your automations: configuration, triggers, actions, best practices and advanced use cases.
Written By Baptiste Lorreyte
Last updated About 1 month ago
Connect a structured task-oriented AI system directly into your CrocoClick automations.
Create.
Retrieve.
Continue.
Delete.
All automatically, based on CRM activity.
No more copying and pasting between tools.
No more manually executing AI tasks.
What is Manus in automations?
Manus is a task-based AI system.
Each task:
Starts with an initial prompt
Executes structured AI logic
Returns a result
Can be continued with new prompts
Once integrated into CrocoClick, you can:
Create AI tasks automatically
Retrieve results
Respond to lifecycle events
Build multi-step AI sequences
This allows you to combine CRM data + AI in powerful, structured automations.
Available triggers (Manus → CrocoClick)
These triggers allow your automations to respond to AI events.
New Task Created
Triggered when a task is created via an automation action.
Task Stopped
Triggered when a task is stopped or completed.
⚠️ Important:
Only tasks created via automation actions trigger these triggers.
Tasks created directly in the Manus interface do not trigger anything.
Available Actions (CrocoClick → Manus)
Your automations can control the entire task lifecycle.
This gives you complete control over AI task management.
Connect your Manus account
You can connect Manus from:
The automation builder
The Integrations page
From an automation
Go to Automation → Workflows
Add a trigger or action
Go to the Apps tab
Select Manus AI
Click on Connect
Enter your API key
From the Integrations page
Go to Settings → Integrations
Locate Manus
Click Connect
Enter your API key
Once connected, triggers and actions become available.
Obtain your Manus API key
To connect your account:
Log in to your Manus account
Go to API settings
Click Create New API Key
Copy the generated key
Paste it when logging in
Keep your API key confidential.
Example of basic configuration
Create or open an automation
Choose a CRM trigger (Form Submitted, Stage Changed, etc.)
Add a Create Task action
Fill in the AI prompt
Store the Task ID (highly recommended)
Add a Wait step if necessary
Add Get Task to retrieve the result
Add the following actions (email, internal note, pipeline, etc.)
Test and publish
Supported dynamic variables
You can use:
{{contact.first_name}} {{contact.email}} {{opportunity.name}} {{custom_values}} This allows you to automatically customize each task.
Best practice: store the Task ID
After creating a task, store the Task ID in a custom field.
Why?
Because this then allows you to:
Retrieve the result with Get Task
Continue the task
Modify the task
Delete the task
Without storing the Task ID, you lose continuity.
For multi-step automations, this is essential.
Concrete use cases
Automatic generation of sales proposals
Trigger: Change to "Proposal requested"
Automation:
Create Task → Generate a draft
Store Task ID
Wait
Get Task
Add internal note
Notify sales rep
Result: Automatically
generated proposal, ready for review.
Automatic search on a lead
Trigger: Form Submitted
Automation:
Create Task → Search company
Store Task ID
Wait
Get Task
Add summary to contact
Notify assigned user
Result:
The sales representative receives an AI analysis even before the first contact.
Site analysis for prospecting
Trigger: Opportunity Created
Automation:
Create Task → Website Analysis
Store Task ID
Wait
Get Task
Generate personalized email
Result: Large-scale personalized
prospecting.
Competitive research and content generation
Trigger: Entry into strategy phase
Automation:
Create Task → Competitive analysis
Store Task ID
Wait
Get Task
Generate differentiated content
Notify marketing team
Result: Strategic
production accelerated by AI.
FAQ
Troubleshooting
If the integration does not work:
Check the validity of your API key
Verify that the integration is connected
Verify that the Task ID is stored correctly
Check the execution logs