---
title: "Connect folk to Emelia - APIANT.ai"
description: "When \"Company Added\" fires in folk, your agent runs \"Add Contact to a Campaign\" in Emelia."
canonical: "https://apiant.ai/connect/folk-to-emelia"
---

# Connect folk to Emelia

When **Company Added** fires in [folk](https://apiant.ai/connections/folk), your agent runs **Add Contact to a Campaign** in [Emelia](https://apiant.ai/connections/emelia). Describe the whole flow and it is built, tested on every scenario and kept running.

folk **11** triggers folk **16** actions Emelia **16** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want folk and Emelia to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What folk can start in Emelia

- When **Company Added** in folk then **Add Contact to a Campaign** in Emelia
- When **Company Custom Field Updated** in folk then **Set a Custom Field to a Contact** in Emelia

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 folk and Emelia

## Triggers and actions 11 triggers · 32 actions

- Trigger

**Company Added**

Triggers when a new company is created or added to a group.

- Trigger

**Company Custom Field Updated**

Triggers when a company custom field (for example tag, status, text, assignee) is updated.

- Trigger

**Company Removed**

Triggers when a company is deleted from the workspace or removed from a group.

- Trigger

**Company Updated**

Triggers when a company basic field (like name, email or URL) in a group is updated.

- Trigger

**Deal Added**

Fires when a new deal is created.

- Trigger

**Deal Removed**

Fires when a deal is deleted from a pipeline.

- Trigger

**Deal Updated**

Fires when a deal is updated (stage change, field update).

- Trigger

**Person Added**

Triggers when a new person is created or added to a group.

- Trigger

**Person Custom Field Updated**

Triggers when a person custom field (for example tag, status, text, assignee) is updated.

- Trigger

**Person Removed**

Triggers when a person is deleted from the workspace or removed from a group.

- Trigger

**Person Updated**

Triggers when a person basic field (like first name, job title, email or URL) in a group is updated.

- Action

**Create Company**

Creates a company in folk, optionally adding it to a group and setting that group's custom fields.

- Action

**Create Deal**

Creates a deal in a folk group, optionally linked to companies and people, and sets that deal type's custom fields.

- Action

**Create Group**

Creates a group in folk. A default "All people" table view is added to the group automatically.

- Action

**Create Note**

Creates a note on a folk person, company or deal. Optionally posts it as a reply to an existing note.

- Action

**Create Person**

Creates a person in folk, optionally adding them to a group and setting that group's custom fields.

- Action

**Create Reminder**

Creates a reminder on a folk person, company or deal, scheduled with an iCalendar recurrence rule.

- Action

**Delete Company**

Deletes a company from folk by its id.

- Action

**Delete Person**

Deletes a person from folk by their id. This also removes their custom fields, notes and associations.

- Action

**Find a Company**

Searches folk companies by name, email or website and returns the matches, with the first one broken out for easy mapping.

- Action

**Find a Person**

Searches folk people by email, full name or phone and returns the matches, with the first one broken out for easy mapping.

- Action

**Get a Company**

Fetches one folk company by id, including its custom field values.

- Action

**Get a Note**

Fetches one folk note by id, with its text, author and the record it is attached to.

- Action

**Get a Person**

Fetches one folk person by id, including their custom field values.

- Action

**List Groups**

Returns the groups in the folk workspace, with each group's id, name and visibility.

- Action

**Update Company**

Updates a folk company. Only the fields you fill in are changed; list fields such as emails replace the whole list.

- Action

**Update Person**

Updates a folk person. Only the fields you fill in are changed; list fields such as emails replace the whole list.

- Action

**Add campaign**

Creates a new email campaign in Emelia with the given name and time zone.

- Action

**Add Contact to a Campaign**

Adds a contact to an Emelia campaign.

- Action

**Add Contact to a List**

Adds a single contact to an Emelia list (and to any campaigns using that list), optionally updating it if it already exists.

- Action

**Add Contact to Blacklist**

Adds an email address or an entire domain to your Emelia blacklist so it is never contacted by your campaigns.

- Action

**Add list**

Creates a new, empty contact list in Emelia.

- Action

**Delete contact**

Deletes a contact (and its company data) from an Emelia contact list; the removal also propagates to campaigns using that list.

- Action

**Get campaign**

Returns the full configuration of an Emelia campaign, including the contact lists attached to it and excluded from it.

- Action

**Get campaign statistics**

Returns sending, open, click and reply statistics for an Emelia campaign, overall and per step.

- Action

**Get contact**

Returns a single contact from an Emelia contact list.

- Action

**List Campaign Contacts**

Returns the contacts enrolled in an email campaign, optionally filtered by an engagement event or a search term.

- Action

**List campaigns**

Returns all campaigns in your Emelia account.

- Action

**List contacts**

Returns the contacts in an Emelia contact list, optionally filtered by search text or an exact email or LinkedIn URL.

- Action

**Search Contact**

Searches a contact list for contacts by exact email, LinkedIn URL, or free text, and returns the matches.

- Action

**Set a Custom Field to a Contact**

Sets the value of a custom field on a contact in an Emelia campaign, identified by email or LinkedIn profile URL.

- Action

**Test Webhook**

Sends a test call to an existing Emelia webhook.

- Action

**Update contact**

Updates an Emelia contact's values; fields you don't send stay unchanged, and changes propagate to campaigns using the contact's list.

## Each app on its own

- [ **folk** folk is the next generation CRM for teams](https://apiant.ai/connections/folk)
- [ **Emelia** Emelia is an all-in-one cold-emailing tool where you can scale easily your cold email, scrape data, and find...](https://apiant.ai/connections/emelia)

Reviews

## What our customers say

## More from folk

- [ **folk to OpenRouter** OpenRouter is a unified interface to AI models.](https://apiant.ai/connect/folk-to-openrouter)
- [ **folk to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/folk-to-hubspot)
- [ **folk to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/folk-to-salesforce)
- [ **folk to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/folk-to-slack)
- [ **folk to Google Sheets** Google Sheets](https://apiant.ai/connect/folk-to-google-sheets)
- [ **folk to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/folk-to-gmail)

## More into Emelia

- [ **HubSpot to Emelia** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-emelia)
- [ **Salesforce to Emelia** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-emelia)
- [ **Slack to Emelia** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-emelia)
- [ **Google Sheets to Emelia** Google Sheets](https://apiant.ai/connect/google-sheets-to-emelia)
- [ **Gmail to Emelia** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-emelia)
- [ **Google Calendar to Emelia** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-emelia)

Questions

## folk and Emelia, answered

###

### What can start an automation from folk?

Any of folk's 11 triggers in the catalog, including Company Added, Company Custom Field Updated, Company Removed and Company Updated. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Emelia when something happens in folk?

Any of Emelia's 16 actions, including Update contact, Add campaign, Add Contact to a Campaign and Add Contact to a List. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Emelia to folk?

Emelia has no triggers in the catalog today, so automations start in folk. If you need the other direction, ask: your agent reads Emelia's API documentation and adds it.

###

### Do I have to build a connector for folk or Emelia?

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 folk and Emelia 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.
