--- title: "Connect iContact to Azure Communication Services Identity - APIANT.ai" description: "When \"New contact\" fires in iContact, your agent runs \"Issue Access Token\" in Azure Communication Services Identity." canonical: "https://apiant.ai/connect/icontact-to-azure-communication-services-identity" --- # Connect iContact to Azure Communication Services Identity When **New contact** fires in [iContact](https://apiant.ai/connections/icontact), your agent runs **Issue Access Token** in [Azure Communication Services Identity](https://apiant.ai/connections/azure-communication-services-identity). Describe the whole flow and it is built, tested on every scenario and kept running. iContact **2** triggers iContact **25** actions Azure Communication Services Identity **4** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want iContact and Azure Communication Services Identity 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 iContact can start in Azure Communication Services Identity - When **New contact** in iContact then **Issue Access Token** in Azure Communication Services Identity - When **New list** in iContact then **Create User** in Azure Communication Services Identity 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 iContact and Azure Communication Services Identity ## Triggers and actions 2 triggers · 29 actions - Trigger **New contact** Triggers when a new contact is added to an iContact client folder, optionally only contacts on a chosen list. - Trigger **New list** Triggers when a new subscriber list is created in an iContact client folder. - Action **Add campaign** Creates a new campaign (sending profile with sender name, sender email and CAN-SPAM mailing address) in an iContact client folder. - Action **Add custom field** Creates a new custom field for contacts in an iContact client folder. - Action **Create Contact** Create a new contact in an iContact client folder. - Action **Create List** Create a new contact list in a client folder. - Action **Create Message** Create a new email message in a client folder. - Action **Delete Contact** Delete an iContact contact by contact ID. - Action **Delete list** Deletes a subscriber list from an iContact client folder. - Action **Get Accounts** List iContact accounts accessible to these credentials. - Action **Get campaign** Returns one iContact campaign (its sending profile, from name and email, and mailing address) by its id. - Action **Get Client Folders** List client folders within an iContact account. - Action **Get Contact** Retrieve a single iContact contact by contact ID. - Action **Get list** Returns one subscriber list from an iContact client folder, including its name, public name and description. - Action **Get message** Returns one email message from an iContact client folder, including its subject, HTML and text bodies, and SpamCheck results. - Action **List Campaigns** List sending campaigns (from-name/email profiles) in a client folder. - Action **List Contacts** List contacts in a client folder, optionally filtered by email or status. - Action **List Custom Fields** List custom fields defined in a client folder. - Action **List Lists** Retrieve all contact lists in a client folder. - Action **List Messages** List email messages in a client folder. - Action **List sends** Returns every email send (pending, sending, released and cancelled) in an iContact client folder, including its message, target lists and segments, schedule, recipient count and status. - Action **List Subscriptions** List subscriptions in a client folder, optionally filtered by contact or list. - Action **Send Message to List** Schedule/send an existing message to one or more lists. - Action **Subscribe Contact to List** Subscribe a contact to a list (creates a subscription). - Action **Unsubscribe Contact from List** Remove a subscription, unsubscribing a contact from a list. - Action **Update Contact** Update an existing iContact contact by contact ID. - Action **Update list** Updates an existing iContact subscriber list's name, public name, description or owner-notification setting. Only the values you supply are changed. - Action **Create User** Creates a Communication Services user identity and, optionally, issues it an access token for chat or calling. - Action **Delete User** Deletes a Communication Services user identity and revokes all of its access tokens. - Action **Issue Access Token** Issues a new access token for a Communication Services user, for use with chat or calling. - Action **Revoke Access Tokens** Revokes every access token issued to a Communication Services user, so they must be issued a new one. ## Each app on its own - [ **iContact** iContact allows your company to create, send, and track your email marketing messages with ease and...](https://apiant.ai/connections/icontact) - [ **Azure Communication Services Identity** REST API for creating Azure Communication Services user identities and issuing scoped access tokens for chat...](https://apiant.ai/connections/azure-communication-services-identity) Reviews ## What our customers say ## More from iContact - [ **iContact to Intercom** Intercom is a customer communications platform for support, engagement, and marketing.](https://apiant.ai/connect/icontact-to-intercom) - [ **iContact to Prismic** Headless CMS API for managing and publishing structured page content for websites and apps.](https://apiant.ai/connect/icontact-to-prismic) - [ **iContact to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/icontact-to-salesforce) - [ **iContact to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/icontact-to-slack) - [ **iContact to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/icontact-to-mailchimp) - [ **iContact to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/icontact-to-stripe) ## More into Azure Communication Services Identity - [ **HubSpot to Azure Communication Services Identity** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-azure-communication-services-identity) - [ **Salesforce to Azure Communication Services Identity** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-azure-communication-services-identity) - [ **Slack to Azure Communication Services Identity** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-azure-communication-services-identity) - [ **Google Sheets to Azure Communication Services Identity** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-azure-communication-services-identity) - [ **Gmail to Azure Communication Services Identity** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-azure-communication-services-identity) - [ **Google Calendar to Azure Communication Services Identity** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-azure-communication-services-identity) Questions ## iContact and Azure Communication Services Identity, answered ### ### What can start an automation from iContact? Any of iContact's 2 triggers in the catalog, including New contact and New list. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Azure Communication Services Identity when something happens in iContact? Any of Azure Communication Services Identity's 4 actions, including Create User, Issue Access Token, Revoke Access Tokens and Delete User. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Azure Communication Services Identity to iContact? Azure Communication Services Identity has no triggers in the catalog today, so automations start in iContact. If you need the other direction, ask: your agent reads Azure Communication Services Identity's API documentation and adds it. ### ### Do I have to build a connector for iContact or Azure Communication Services Identity? 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 iContact and Azure Communication Services Identity 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.