Zapier
Connect Zapier MCP Client to Clics for analytics automations without a native Clics app.
Connect Clics to Zapier
Zapier’s MCP Client can call Clics tools from Zaps and Agents. This is a remote MCP connection, not a native Clics Zapier app.
1. Use the Clics remote MCP URL
https://api.clics.dev/v1/mcp
2. Add the connection in Zapier
Open Apps, select Add connection, and search for MCP Client. Use:
| Field | Value |
|---|---|
| Server URL | Your Clics remote MCP URL |
| Transport | Streamable HTTP |
| OAuth | Yes |
| Bearer token | Leave empty |
Save the connection, complete WorkOS authorization, and give it a recognizable name such as Clics MCP. If your Zapier MCP Client does not support OAuth discovery, use the Clics REST API instead.
3. Run a Clics tool
In a Zap or Agent, choose MCP Client and use Run Read-Only Tool for analytics queries or Run Tool for operations that can change projects, goals, or funnels.
Read-only and write actions
Start with Run Read-Only Tool when building reports, alerts, and lookups. Use Run Tool only when the Zap must create or change a Clics project, goal, or funnel.
For write actions:
- Add a Filter or approval step before the MCP action
- Include the project ID explicitly instead of asking an agent to guess
- Test with a non-critical project before enabling the Zap
Example Zaps
Send a weekly traffic digest
- Trigger the Zap every Monday.
- Run
query_statsfor the previous seven days. - Parse the returned structured content.
- Send the summary through Slack, Microsoft Teams, Gmail, or another destination.
Alert on goal performance
Retrieve goal data on a schedule, add a Filter for your conversion threshold, then notify the responsible teammate only when the condition is met.
Create goals from an intake form
Collect a project ID, goal name, and match rule from a form. Add an approval step, then call create_goal with the approved values.
Working with MCP responses
Clics returns both text and structured content. When Zapier exposes the parsed structured content, map those fields directly into later steps. If only text is available, parse the JSON string before referencing individual metrics.
Avoid sending the complete raw response to end users. Select and label the few metrics the destination actually needs.
Troubleshooting
| Issue | What to check |
|---|---|
| Connection is not listed | Refresh the Zap editor after adding it |
| Immediate reconnect prompt | Streamable HTTP is selected and the full URL is present |
401 |
Reconnect and complete the WorkOS authorization flow |