When IP lookup data is captured in IP2Proxy, update contact details or tags in ActiveCampaign.
When IP lookup data is captured in IP2Proxy, update contact details or tags in ActiveCampaign.
See all IP2Proxy + Active Campaign integrations or talk to a human
Opens Claude with Knit filled in: click Continue. Claude web and desktop share one connector list. Or paste this link in Settings > Connectors > Add custom connector.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents claude
Run in your own terminal, then restart Claude Code. Adds the server, the Knit skill and a CLAUDE.md note.
Turn on developer mode, then create a connector named Knit with this link and No Auth.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents codex
Run in your own terminal (not through Codex), then start a new Codex session.
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents antigravity
Run in your own terminal, then reload MCP servers (/mcp in the CLI, refresh in the IDE).
curl -fsSL https://raw.githubusercontent.com/knitapi/knit-plugin/main/plugins/knit/skills/knit/scripts/install.sh | bash -s -- --agents cursor
Run in your own terminal, restart Cursor, then paste the note it prints into User Rules.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
IP2Proxy Explore IP2Proxy →
TriggersFires when a job, build or file conversion finishes in IP2Proxy.
Fires when a job, build or API request fails in IP2Proxy.
Calls an IP2Proxy endpoint with data from an earlier step.
Creates a PDF, image or converted file with IP2Proxy.
Checks or enriches a phone number, address or IP with IP2Proxy.
Active Campaign Explore Active Campaign →
TriggersFires when a new lead or contact is captured in Active Campaign.
Fires when a contact enters an automation in Active Campaign.
Fires when a field on a contact changes in Active Campaign.
Fires when a contact unsubscribes in Active Campaign.
Creates or updates a contact in Active Campaign.
Adds a contact to a workflow or campaign in Active Campaign.
Sends an email or message to a contact via Active Campaign.
Changes a contact's tags in Active Campaign.
More IP2Proxy + Active Campaign workflows
See all IP2Proxy + Active Campaign integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “When IP lookup data is captured in IP2Proxy, update contact details or tags in ActiveCampaign.” between IP2Proxy and Active Campaign?
Yes — describe it in the box above and Knit's Integrations Agent researches IP2Proxy and Active Campaign's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
What is the benefit of connecting IP2Proxy to Active Campaign?
Connecting IP2Proxy to Active Campaign ensures marketing messages automatically pause or launch based on software deployment events or active technical issue resolutions.
Can customer bug reports in Active Campaign trigger technical tasks in IP2Proxy?
Yes, when high-value contacts encounter issues or enter support workflows in Active Campaign, engineering tasks can be automatically logged in IP2Proxy for investigation.