Integration
Connect eSputnik to Brand.dev
When New Contact fires in eSputnik, your agent runs Find rows in a collection in Brand.dev. 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 eSputnik and Brand.dev 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 eSputnik can start in Brand.dev
When New Contact in eSputnik
then Find rows in a collection in Brand.dev
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 eSputnik and Brand.dev
Triggers and actions 2 triggers · 31 actions
- New Contact
Triggered when a new contact is created in eSputnik, optionally limited to contacts matching the details you enter.
- New Contact in Segment
Triggers when a contact is added to the eSputnik segment you choose.
- Add contact to segment
Adds one or more contacts to a static segment in eSputnik, identified by contact IDs or external customer IDs.
- Add emails to unsubscribed list
Adds one or more email addresses to the eSputnik list of unsubscribed contacts.
- Add/Update Contact
Adds a new contact or updates the existing matching contact, including its channels, address and additional fields, and returns the contact's ID.
- Delete contact
Deletes a contact by its eSputnik contact ID, optionally erasing all of the contact's data permanently.
- Delete contact from segment
Removes one or more contacts from a static segment, identified by their eSputnik contact IDs or external customer IDs.
- Find contacts
Returns up to 500 contacts that match the specified external ID, email address, phone number, first name or last name.
- Get contact
Returns an eSputnik contact by ID, including its channels, address, segments and additional field values. An error occurs if the contact is not found.
- List segments
Returns the contact segments in the eSputnik account, optionally narrowed by name, with each segment's id, name and type.
- Send Email
Sends an email message to one or more recipients. A new contact is created for any address that does not already exist in eSputnik.
- Send Event
Sends a backend event for a contact to eSputnik, where it can start workflows and supply dynamic content for messages.
- Send Viber message
Sends a Viber message to a list of phone numbers or to a segment, and returns the queueing result for each recipient. A new contact is created for a phone number that does not exist yet.
- Subscribe Contact
Subscribes a contact through a double opt-in flow, creating an unconfirmed contact if none exists or updating the existing one, and returns the contact's ID and email subscription status.
- Add a monitor
Create a website change monitor.
- Delete a collection
Delete a WebDBs data collection.
- Delete a monitor
Delete a website change monitor.
- Extract Products From a Brand's Website
Beta feature: Extract product information from a brand's website. Brand.dev will analyze the website and return a list of products with details such as name, description, image, pricing, features, and more.
- Find rows in a collection
Query rows stored in a WebDBs data collection.
- Get a batch
Retrieve a batch's status by ID.
- Get a monitor
Retrieve a website change monitor by ID.
- Get batch results
Retrieve the results of a completed batch.
- List batches
List submitted batches.
- List collections
List WebDBs data collections.
- List monitors
List website change monitors.
- Query Website Data Using AI
Use AI to extract specific data points from a brand's website. The AI will crawl the website and extract the requested information based on the provided data points.
- Retrieve Brand Data by Company Name
Retrieve brand information using a company name. This endpoint searches for the company by name and returns its brand data.
- Retrieve person
Retrieve a person's profile data.
- Retrieve Simplified Brand Data by Domain
Returns a simplified version of brand data containing only essential information: domain, title, colors, logos, and backdrops. This endpoint is optimized for faster responses and reduced data transfer.
- Run a monitor
Trigger a website change monitor to run immediately.
- Search company news
Search for recent news articles about a company or brand.
- Update a collection
Update a WebDBs data collection's configuration.
- Update a monitor
Update a website change monitor's configuration.
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 eSputnik
eSputnik to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
eSputnik to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
eSputnik to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
eSputnik to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
eSputnik to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
eSputnik to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Brand.dev
Questions
eSputnik and Brand.dev, answered
What can start an automation from eSputnik?
Any of eSputnik's 2 triggers in the catalog, including New Contact and New Contact in Segment. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Brand.dev when something happens in eSputnik?
Any of Brand.dev's 19 actions, including Update a collection, Update a monitor, Add a monitor and Extract Products From a Brand's Website. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Brand.dev to eSputnik?
Brand.dev has no triggers in the catalog today, so automations start in eSputnik. If you need the other direction, ask: your agent reads Brand.dev's API documentation and adds it.
Do I have to build a connector for eSputnik or Brand.dev?
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 eSputnik and Brand.dev 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.