Integration
Connect Kulea to Fullstory
When Form Completed fires in Kulea, your agent runs Add user in Fullstory. 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 Kulea and Fullstory 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 Kulea can start in Fullstory
When Form Completed in Kulea
then Add user in Fullstory
When New or Updated CRM Data in Kulea
then Set User Properties in Fullstory
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 Kulea and Fullstory
Triggers and actions 9 triggers · 12 actions
Trigger
Email Bounced EventTriggers when a Kulea email hard-bounces.
Trigger
Email Opened EventTriggers when a contact opens a Kulea email.
Trigger
File Downloaded EventTriggers when a contact downloads a file from Kulea.
Trigger
Form CompletedTriggers when a contact completes a Kulea form.
Trigger
Landing Page Visit EventTriggers when a contact visits a Kulea landing page.
Trigger
Link Clicked EventTriggers when a contact clicks a link in a Kulea email.
Trigger
New or Updated CRM DataTriggers when a Kulea contact is added or its CRM data changes.
Trigger
UnsubscribeTriggers when a contact unsubscribes from Kulea emails.
Trigger
Webpage VisitTriggers when a contact visits a tracked page on your own website.
Action
Archive ContactArchives a Kulea contact, which also unsubscribes it.
Action
Create New ContactCreates a new Kulea contact. The email address must be unique.
Action
Find ContactFinds Kulea contacts whose email matches the address you give.
Action
Get ContactReturns one Kulea contact by its ID.
Action
List Contact FieldsReturns the fields on Kulea contact records and their types.
Action
Add annotationCreates an annotation in Fullstory to mark an event such as a release on your session and metric timelines.
Action
Add userCreates a Fullstory user, or updates the existing user with the same User ID.
Action
Delete userDeletes a single Fullstory user by their Fullstory-generated user id.
Action
Find usersFinds Fullstory users matching a uid, email, display name or identified status.
Action
Get userReturns the details of a single Fullstory user, including their custom user properties.
Action
Set User PropertiesUpdates an existing Fullstory user's custom properties, display name, email or application user id.
Action
Track EventCreates a custom server event in Fullstory, optionally attached to an existing session or 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 Kulea
Kulea to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Kulea to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Kulea to MailchimpMailchimp marketing automation and email platform.
Kulea to StripeStripe is a payment processing platform for online businesses.
Kulea to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Kulea to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Fullstory
HubSpot to FullstoryHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to FullstorySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to FullstorySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to FullstoryGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to FullstoryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to FullstoryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Kulea and Fullstory, answered
What can start an automation from Kulea?
Any of Kulea's 9 triggers in the catalog, including Form Completed, New or Updated CRM Data, Email Bounced Event and Email Opened Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Fullstory when something happens in Kulea?
Any of Fullstory's 7 actions, including Add annotation, Add user, Find users and Get user. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fullstory to Kulea?
Fullstory has no triggers in the catalog today, so automations start in Kulea. If you need the other direction, ask: your agent reads Fullstory's API documentation and adds it.
Do I have to build a connector for Kulea or Fullstory?
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 Kulea and Fullstory 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.