Integration
Connect Intulse and StoryChief
When Queue Event Created fires in Intulse, your agent runs Create Calendar Event in StoryChief, or New Contact in StoryChief to Add contact in Intulse. 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 Intulse and StoryChief 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Intulse and StoryChief can do together
From Intulse to StoryChief
When Queue Event Created in Intulse
then Create Calendar Event in StoryChief
When Text Message Received in Intulse
then Add Contact to List in StoryChief
From StoryChief to Intulse
When New Contact in StoryChief
then Add contact in Intulse
When Post Published in StoryChief
then Send Text Message in Intulse
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 Intulse and StoryChief
Triggers and actions 9 triggers · 64 actions
Trigger
Call EndedTriggers when a call in your Intulse organization ends and appears in the call log.
Trigger
Queue Event CreatedTriggers when a new event happens in one of your Intulse call queues.
Trigger
Text Message ReceivedTriggers when a new SMS/MMS text message appears in your Intulse organization.
Action
Add contactCreates a new user contact in Intulse with name, company, phone numbers and emails.
Action
Delete contactDeletes a user contact from Intulse.
Action
Get extensionReturns one phone extension with its name, device state, and Do Not Disturb, call waiting and call forwarding status.
Action
Get userReturns a specific Intulse user by ID, including name, email, mobile, extension and admin status.
Action
List callsReturns the organization's calls that started within a date range, optionally narrowed by an advanced filter. Requires a master API key.
Action
List extensionsReturns every extension configured in your Intulse account, with its name, device state and DND, call waiting and call forwarding status. Requires an admin user or organization API key.
Action
List queuesReturns the call queues in your Intulse organization with their live stats, members and waiting callers.
Action
List usersReturns the users in your Intulse organization, with their names, email, mobile number, extension and admin status.
Action
List voicemailsReturns every voicemail box in your organization with its folders and messages, including caller, duration, date and transcription.
Action
Originate CallStarts a phone call from an Intulse extension to a target number.
Action
Send Text MessageSends an SMS text message from one of your Intulse numbers.
Action
Update contactUpdates an existing user contact in Intulse, such as its name, company, phone numbers, emails and notes.
Action
Update Extension Call Forward AlwaysTurns Call Forward Always on or off for an Intulse extension and sets where calls forward to.
Action
Update Extension DNDTurns Do-Not-Disturb on or off for an Intulse extension.
Trigger
New ContactTriggers when a new contact is added.
Trigger
Post PublishedTriggers when a social media post is published.
Trigger
Published or Updated StoryTriggers when a story is published or a published story is updated.
Trigger
Published StoryTriggers when a story is published.
Trigger
Story CreatedTriggers when a new story is created.
Trigger
Story ScheduledTriggers when a story is scheduled for publication.
Action
Add Contact to ListAdds a new contact to a contact list.
Action
Batch Subscribe ContactsAdds or updates many contacts in a contact list at once.
Action
Create AuthorCreates an author.
Action
Create Calendar EventAdds an event to the StoryChief content calendar.
Action
Create CategoryCreates a category.
Action
Create Social PostCreates a social media post on one or more channels, published now or scheduled.
Action
Create StoryCreates a story in StoryChief.
Action
Create TagCreates a tag.
Action
Create TaskCreates a task.
Action
Delete AuthorDeletes an author, moving their stories to a replacement author.
Action
Delete CategoryDeletes a category.
Action
Delete ContactDeletes a contact from the account.
Action
Delete TagDeletes a tag.
Action
Find ContactFinds a contact by email address.
Action
Find Contact in ListFinds a contact in a contact list by email address.
Action
Get AuthorReturns an author.
Action
Get CategoryReturns a category.
Action
Get ContactReturns a contact with the lists they are on.
Action
Get Contact in ListReturns a contact from a contact list.
Action
Get Contact ListReturns a contact list.
Action
Get DestinationReturns a publishing channel.
Action
Get MeReturns the user the API key belongs to.
Action
Get Social PostReturns a social media post with its metrics.
Action
Get StoryReturns a story with its content, tags, categories and author.
Action
Get TagReturns a tag.
Action
Get TaskReturns a task.
Action
Get UserReturns a user.
Action
Invite UserInvites a new user to the StoryChief account.
Action
List AuthorsReturns the authors in the account.
Action
List CategoriesReturns the categories in the account.
Action
List Contact ListsReturns the contact lists in the account.
Action
List ContactsReturns every contact in the account with the lists they are on.
Action
List Contacts in ListReturns the contacts in a contact list.
Action
List DestinationsReturns the publishing channels connected to the account.
Action
List Social PostsReturns social media posts, filtered by channel or status.
Action
List StoriesReturns stories, filtered by status, language, author or update date.
Action
List Story CommentsReturns the comments on a story.
Action
List TagsReturns the tags in the account.
Action
List TasksReturns tasks, filtered by status, assignee or client workspace.
Action
List UsersReturns the users of the StoryChief account.
Action
Purge Contact ListRemoves every contact from a contact list.
Action
Remove Contact from ListRemoves a contact from a contact list.
Action
Update AuthorUpdates an author.
Action
Update CategoryRenames a category.
Action
Update ContactUpdates a contact.
Action
Update Contact in ListUpdates a contact and its subscription status in a contact list.
Action
Update StoryUpdates a story.
Action
Update TagRenames a tag.
Action
Update TaskUpdates a task.
Action
Update UserUpdates a user.
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 Intulse
Intulse to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Intulse to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Intulse to MailchimpMailchimp marketing automation and email platform.
Intulse to StripeStripe is a payment processing platform for online businesses.
Intulse to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Intulse to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into StoryChief
HubSpot to StoryChiefHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to StoryChiefSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to StoryChiefSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to StoryChiefGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to StoryChiefGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to StoryChiefGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Intulse and StoryChief, answered
What can start an automation from Intulse?
Any of Intulse's 3 triggers in the catalog, including Queue Event Created, Text Message Received and Call Ended. Describe the moment in plain language and your agent picks the right one.
What can your agent do in StoryChief when something happens in Intulse?
Any of StoryChief's 50 actions, including Create Author, Create Calendar Event, Create Category and Create Social Post. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from StoryChief to Intulse?
Yes. When something happens in StoryChief, your agent can act in Intulse too. This page covers both directions: StoryChief's triggers and Intulse's actions are listed here as well.
Do I have to build a connector for Intulse or StoryChief?
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 Intulse and StoryChief 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.