Integration
Connect Getsitecontrol and Pipefile
When New Contact fires in Getsitecontrol, your agent runs Create Contact in Pipefile, or File Request Created in Pipefile to Add contact field in Getsitecontrol. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Getsitecontrol and Pipefile to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Getsitecontrol and Pipefile can do together
From Getsitecontrol to Pipefile
When New Contact in Getsitecontrol
then Create Contact in Pipefile
From Pipefile to Getsitecontrol
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Getsitecontrol and Pipefile
Triggers and actions 3 triggers · 36 actions
- New Contact
Triggers when a contact is added to a site.
- New Submission
Triggers when a visitor submits a Getsitecontrol form.
- Add contact field
Creates a custom contact field on a Getsitecontrol site and returns it, including the id contacts use for its values.
- Add segment
Creates a contact segment from a name and a set of conditions, and returns the new segment.
- Create Tag
Creates a contact tag.
- Delete contact field
Deletes a custom contact field from a Getsitecontrol site. Contacts keep their stored values for the field.
- Delete segment
Deletes a contact segment that no automation, broadcast or other segment uses. The contacts in it are not affected.
- Delete Tag
Deletes a contact tag.
- Find Contacts
Finds contacts by email, text search, status, tag or segment.
- Get broadcast
Returns one e-mail broadcast with its status, sender, audience, schedule, A/B test settings and folder.
- Get Contact
Returns one contact.
- Get Form Response
Returns one form response.
- Get segment
Returns one contact segment with its name, conditions and folder.
- Get Site
Returns one Getsitecontrol site.
- Get Tag
Returns one tag on a Getsitecontrol site by its ID, with its name and creation date.
- List broadcasts
Returns the e-mail broadcasts (campaigns) of a Getsitecontrol site, with status, subject, sender, audience, schedule and folder.
- List Contact Fields
Returns the custom contact fields defined on a site.
- List folders
Returns every folder of one kind (widgets, segments, broadcasts or automations) on a site, with how many live items each folder holds.
- List Form Responses
Returns form responses submitted on a site, optionally for one widget or a date range.
- List Segments
Returns the contact segments on a site.
- List Sites
Returns the Getsitecontrol sites your API key can access.
- List Tags
Returns the contact tags on a site.
- List Widgets
Returns the widgets (popups, forms and bars) on a site.
- Run email automation for contact
Starts an email automation (with a manual or webhook trigger) for one contact, either an existing contact or one created or updated by email.
- Update contact field
Renames a custom contact field on a Getsitecontrol site. The field's id and the values contacts hold in it stay the same.
- Update segment
Renames a segment or replaces its conditions, and returns the updated segment.
- Update Tag
Renames a tag on a Getsitecontrol site. Contacts that carry the tag keep it.
- Update widgets
Updates up to 100 widgets at once: turns them on or off, renames them, moves them to a folder, or changes notification e-mails, reCAPTCHA and the e-mail quality filter. Returns the result for each widget.
- File Request Created
Triggers when a file request is created.
- Add File Request From Template
Create a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.
- Create Contact
Add to contacts
- Delete Contact
Delete a contact by id. Returns 204 No Content on success.
- Get Contact
Retrieve one contact by id.
- Get File Request
Retrieve detailed information about one file request by id, including contents, items, files, and tracking events.
- List Contacts
Retrieve a paginated list of contacts, filterable by name/email/phone partial match.
- List File Request Templates
Retrieve the list of file request templates available for creating new file requests, with optional name search.
- Search File Requests
Finds all file requests matching this search query (contact name, email, tags, etc).
- Send Request
Create and send a new request
- Update Contact
Update name/email/phone of an existing contact by id.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Getsitecontrol
Getsitecontrol to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Getsitecontrol to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Getsitecontrol to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Getsitecontrol to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Getsitecontrol to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Getsitecontrol to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Pipefile
Instagram to PipefileInstagram is a social media platform for sharing photos, videos, and stories.
CM.com to PipefileCM.com — create excellent conversational customer experiences and turn any conversation into a conversion.
EARLY to PipefileEARLY is a Time Tracking App: Effortless, Smart, and Secure.
Questions
Getsitecontrol and Pipefile, answered
What can start an automation from Getsitecontrol?
Any of Getsitecontrol's 2 triggers in the catalog, including New Contact and New Submission. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pipefile when something happens in Getsitecontrol?
Any of Pipefile's 10 actions, including Create Contact, Send Request, Update Contact and Add File Request From Template. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pipefile to Getsitecontrol?
Yes. When something happens in Pipefile, your agent can act in Getsitecontrol too. This page covers both directions: Pipefile's triggers and Getsitecontrol's actions are listed here as well.
Do I have to build a connector for Getsitecontrol or Pipefile?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Getsitecontrol and Pipefile without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.