Integration
Connect Coworks to TwitterAPIs
When Contact Updated fires in Coworks, your agent runs Send direct message in TwitterAPIs. 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 Coworks and TwitterAPIs 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 Coworks can start in TwitterAPIs
When Contact Updated in Coworks
then Send direct message in TwitterAPIs
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 Coworks and TwitterAPIs
Triggers and actions 10 triggers · 25 actions
- Contact Updated
Triggers when a contact in your Coworks CRM is created or changed.
- CRM Entry Updated
Triggers when a CRM contact or lead is added or changed in Coworks.
- Lead Updated
Triggers when a lead in Coworks is created or changed, including changes to its status, custom fields, or any other returned detail.
- Member Deactivate
Triggered when a member is deactivated and is no longer an active member.
- Member Updated
Triggers when a member is added or any of a member's details change.
- New Checkin
Triggered when a new check-in is recorded for a member, visitor or passport holder in your Coworks community.
- New Contact
Triggered when a new contact is created in your Coworks CRM.
- New CRM Entry
Triggered when a new CRM entry, either a contact or a lead, is created.
- New Lead
Triggers when a new lead is created in the Coworks CRM.
- New Member
Triggered when a new member is created in your Coworks community.
- Get room occupancy
Returns the rooms at a campus with their occupancy, optionally limited to one room type.
- List active memberships
Returns the community's paid memberships, optionally limited to one status. Free subscriptions are not included.
- List checkins
Returns check-ins for your Coworks community, optionally filtered by campus, check-in type, date range or person name.
- List CRM contacts and leads
Returns the contacts and leads in your Coworks CRM, optionally filtered by campus, type, lead status, source and date.
- List members
Returns the members of your Coworks community, optionally narrowed to specific teams or a campus, and optionally including inactive members.
- List rooms
Returns the rooms at a campus, optionally narrowed to one room type.
- List teams
Returns the teams in your Coworks community, optionally narrowed by team, campus, or join date.
- Add bookmark
Bookmark a tweet on the X account behind the connection's registered session.
- Add media upload
Uploads a base64-encoded image as the connected X account and returns a media_id to attach to a new tweet.
- Add tweet
Create a new tweet or reply.
- Delete tweet
Permanently delete a tweet owned by the connected X account, identified by its ID or status URL.
- Find tweets by advanced search
Searches tweets on X using advanced search operators and returns about 20 matching tweets.
- Find users by keyword
Search Twitter/X accounts by keyword, matching display name, handle and bio.
- Follow user
Follow a user as the connected X account. Requires a registered X session on the account.
- Get tweet
Fetch one or more tweets by ID.
- Get user info
Fetch a Twitter/X user's profile by username.
- Like tweet
Like (favorite) a tweet as the connected X account. Requires a registered X session on the TwitterAPIs account.
- List tweet replies
Lists the direct replies to a tweet, identified by its ID or status URL. Returns about 20 replies per page.
- List user followers
Returns one page (about 20 to 100) of the accounts that follow a user, as full user profiles.
- List user followings
Lists the accounts a given X/Twitter user follows, one page at a time.
- List user tweets
Lists a page (about 20) of a user's most recent public tweets, including retweets and replies.
- Retweet tweet
Retweet a tweet as the authenticated X account. Requires a registered X session on the TwitterAPIs account.
- Send direct message
Send a direct message to a user.
- Unfollow user
Unfollow a user as the connected X account. Requires a registered X session on the account.
- Update profile
Updates the display name, bio, location or website link on the connected X account. Only the fields you fill in are changed; blank fields keep their current values.
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 Coworks
Coworks to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Coworks to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Coworks to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Coworks to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Coworks to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Coworks to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into TwitterAPIs
ChMeetings to TwitterAPIsChMeetings is a church management software that helps manage people, services, events, donations, and more.
Questions
Coworks and TwitterAPIs, answered
What can start an automation from Coworks?
Any of Coworks's 10 triggers in the catalog, including Contact Updated, CRM Entry Updated, Lead Updated and Member Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in TwitterAPIs when something happens in Coworks?
Any of TwitterAPIs's 18 actions, including Send direct message, Update profile, Add media upload and Add tweet. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from TwitterAPIs to Coworks?
TwitterAPIs has no triggers in the catalog today, so automations start in Coworks. If you need the other direction, ask: your agent reads TwitterAPIs's API documentation and adds it.
Do I have to build a connector for Coworks or TwitterAPIs?
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 Coworks and TwitterAPIs 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.