Integration
Connect Blink and TimeRex
When New Form Submission fires in Blink, your agent runs Get Event in TimeRex, or Event Created in TimeRex to Post to Feed in Blink. 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 Blink and TimeRex 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 Blink and TimeRex can do together
From Blink to TimeRex
When New Form Submission in Blink
then Get Event in TimeRex
From TimeRex to Blink
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 Blink and TimeRex
Triggers and actions 2 triggers · 18 actions
- New Form Submission
Triggers when someone submits the chosen Blink form.
- Archive Feed Post
Dismisses a feed post for everyone who received it.
- Archive Feed Post for User
Dismisses a feed post for one user who received it.
- Find Feed Post by External ID
Finds a feed post's ID from the external ID it was sent with.
- Find Users
Returns users in your Blink organisation, optionally filtered by email, employee ID or user ID.
- List Feed Categories
Returns the feed categories defined for your Blink integration.
- List Forms
Returns the forms in your Blink organisation.
- Post to Feed
Posts a new card to the feeds of the selected users or teams.
- Update Feed Post
Edits the card of a feed post that was already sent.
- Event Created
Triggers when a new event is booked on a TimeRex calendar.
- Cancel Event
Cancels a booked TimeRex event, with an optional reason.
- Create One-Time URL
Creates a single-use booking URL for a TimeRex calendar.
- Get Calendar
Returns one TimeRex booking calendar by its ID.
- Get Event
Returns one booked TimeRex event by its ID, with guest and meeting details.
- Get One-Time URL
Returns a TimeRex one-time booking URL and the event booked through it, if any.
- Get Primary Team
Returns the TimeRex team the API key belongs to.
- Get Team
Returns one TimeRex team by its ID.
- List Calendar Events
Returns the events booked on a TimeRex calendar, optionally within a time range.
- List Calendars
Returns the booking calendars of a TimeRex team.
- List Teams
Returns the TimeRex teams available to the API key.
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 Blink
Blink to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Blink to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Blink to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Blink to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Blink to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Blink to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into TimeRex
Questions
Blink and TimeRex, answered
What can start an automation from Blink?
Any of Blink's 1 trigger in the catalog, including New Form Submission. Describe the moment in plain language and your agent picks the right one.
What can your agent do in TimeRex when something happens in Blink?
Any of TimeRex's 10 actions, including Create One-Time URL, Get Calendar, Get Event and Get One-Time URL. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from TimeRex to Blink?
Yes. When something happens in TimeRex, your agent can act in Blink too. This page covers both directions: TimeRex's triggers and Blink's actions are listed here as well.
Do I have to build a connector for Blink or TimeRex?
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 Blink and TimeRex 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.