Fingertip
Web PlatformConnect AI agents to Fingertip, the all-in-one platform for business sites with bookings, a store, forms, and contacts. Agents read sites and blog posts, create contacts, accept, decline, or reschedule bookings, and list orders so site operations run without manual clicks.
What This Integration Enables
Fingertip collapses a business into one page: the link in the bio is also the calendar, the storefront, the contact form, and the blog. That is a genuinely different shape from a website builder, and it changes what an agent should be doing here. The connector is deliberately read-heavy across the site itself, meaning List Sites, Get Site, Get Page, List Blog Posts, and Get Site Analytics, because the page is designed to be edited by its owner in a builder that takes minutes. The write power is concentrated somewhere more interesting.
That somewhere is the booking lifecycle. Accept Booking, Decline Booking, Cancel Booking, Complete Booking, and Reschedule Booking are the operations that decide whether a customer gets served, and two of them can charge that customer. Around them sit the commercial reads and the one commercial write: List Orders for what sold, List Site Contacts for who has been captured, and Create Site Contact for adding someone the site itself never met, such as a lead from an offsite form or a walk-in the owner wants in the same list as everyone else. Delete Site and Delete Page are also here, and both are permanent, which is worth knowing before a cleanup flow is pointed at an account holding several sites. There are no triggers, so a Fingertip flow starts on a schedule or on an event in another system, and the sweep pattern in the primary workflow is the usual shape.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A booking queue that clears itself before lunch
Every hour the agent calls List Bookings filtered to pending. For each request it checks the requested time against the owner's calendar and against the bookings the site has already confirmed, so a double booking is caught before it becomes an apology. Requests that fit are confirmed with Accept Booking. Requests that collide with existing work are cleared with Decline Booking and the reason is recorded, so the customer is not left waiting on silence. Requests that are close but not clean, meaning a slot ten minutes into a confirmed job or a customer asking for a time outside normal hours, go to the owner as a short list rather than being decided by an agent guessing at how flexible the day is.
Site contacts that reach the systems that use them
Fingertip captures contacts on the site, and left alone they stay there. On a daily run the agent reads List Site Contacts, compares against the CRM in HubSpot, and creates the ones that are new with the source recorded as the site. The flow runs the other way too: a lead that arrives through an offsite form, a phone call, or an event list becomes a Create Site Contact so the site's own list matches the business's list. Alongside it, List Orders pulls the store activity and Get Site Analytics pulls the traffic figures, and both land in a weekly summary in Slack so the owner sees what sold and what was visited without opening three dashboards.
The end of the day, when bookings become money
At close of business the agent reads the day's bookings and sorts them. Anything the customer attended and paid for is straightforward, and Complete Booking marks it done. The rest is the interesting part. A customer who did not appear, a customer who canceled an hour before, a customer whose job ran so long the next appointment never happened: each of those is a judgment about whether to charge a fee, and the connector makes charging possible in one call. The agent assembles the facts for each one, including the booking history from List Bookings and whether the person is a repeat customer from List Site Contacts, and then stops.
Human-in-Loop Highlight
The gate on this connector sits exactly where money leaves a customer's account, and Fingertip puts two actions there. Cancel Booking takes an optional fee. Complete Booking can be marked as a charge or a no-show. Both are single calls, both hit a real person who chose this business, and neither is a decision an agent can make well, because the inputs that matter are not in the API. Whether a no-show gets charged depends on whether the customer texted, whether they are a regular, whether the weather closed the road, and whether the owner wants them back next month. None of that is a field.
So the agent runs the day right up to that line and then asks in Slack, naming what it knows: "End of day, 3 bookings need a fee decision. Dana R, 2pm cut and color, did not attend, first booking with you, no message. Marcus L, 4pm, canceled at 3:40, fourth booking this year, said his kid was sick. Priya S, 5:30, arrived 40 minutes late and the job did not happen. Charge a no-show fee on any of these?" The owner answers in one message, and the agent executes Complete Booking or Cancel Booking with the fee exactly as told. That is human-in-the-loop applied where it earns its place: the tedious end-of-day reconciliation moves to the agent, and the call that costs a customer money and possibly the relationship stays with the person who has to see them again.
Two other actions deserve a hard boundary for a different reason. Delete Site and Delete Page are permanent, and on an account that holds several sites a cleanup flow with a slightly wrong Site ID removes a live business page rather than the abandoned draft it was aimed at. Neither belongs in an automatic path. If an agent is going to propose a deletion, it should propose it with the site name, the URL, and its recent figures from Get Site Analytics attached, and let a person be the one who confirms which site is actually the dead one.
Agent Capabilities
17 actionsSites and Pages
6- List Sites Lists the sites in the account and is the source of the Site IDs every other site-scoped operation needs. The first call in almost any Fingertip flow, and the reference an agent should resolve against rather than carrying a hard-coded ID.
- Get Site Retrieves a single site by ID with its configuration. Used to confirm which site a flow is about to write to before it writes.
- Get Site Analytics Returns views and engagement figures for a site. Used in weekly summaries and as supporting evidence when a person is being asked to decide whether a site is still worth keeping.
- Delete Site Permanently deletes a site. There is no undo, and on a multi-site account a wrong Site ID removes a live business page, so this belongs behind a confirmed decision rather than in a scheduled cleanup.
- Get Page Retrieves a page by ID. Used to read the current content of a page before referencing it elsewhere or reporting on it.
- Delete Page Permanently deletes a page. Same caution as Delete Site: the call succeeds quietly and the page does not come back.
Blog
2- List Blog Posts Lists a site's blog posts with sorting. Used to check what has been published, to feed a content index, or to build a digest of recent posts for a newsletter.
- Get Blog Post Retrieves a single blog post. Used when a flow needs the post's body rather than just its title, for example to syndicate it or to summarize it elsewhere.
Contacts
2- List Site Contacts Lists the contacts a site has captured. The read behind CRM synchronization and behind any decision that depends on whether a person is new or returning.
- Create Site Contact Adds a contact to a site by email. Used to bring in people the site itself never met, such as leads from an offsite form, an event list, or a phone call, so the site's list matches the business's list.
Bookings
6- List Bookings Lists a site's bookings with a status filter. The read behind the pending queue, the day's schedule, and any history a person needs before deciding on a fee.
- Accept Booking Confirms a pending booking. The routine half of booking triage, safe to automate once the slot has been checked against the calendar and against existing confirmations.
- Decline Booking Declines a pending booking. Used when a requested slot cannot be served, and paired with a message so the customer is not left waiting on silence.
- Cancel Booking Cancels a booking that was already confirmed, with an optional fee. The fee is what makes this a gated action: it charges a real customer in the same call that cancels their appointment.
- Complete Booking Marks a booking completed, including the option to record it as a charge or a no-show. The no-show path takes money from someone who did not turn up, which is a judgment about the relationship rather than a data operation.
- Reschedule Booking Moves a booking to a new time. Used when a slot has to shift and the customer has already agreed to the new one, which makes it the constructive alternative to canceling with a fee.
Orders
1- List Orders Lists the store orders placed on a site. Used for revenue summaries, for reconciliation against the accounting system, and for spotting an order that never turned into a fulfilled job.
Frequently Asked Questions
What can FlowRunner do with Fingertip?
FlowRunner agents can run List Sites, Get Site, and Get Site Analytics in Fingertip, plus 14 more actions.
Does connecting Fingertip to FlowRunner require OAuth?
No. Fingertip connects to FlowRunner with an API key, no OAuth flow required.
Can Fingertip trigger a FlowRunner workflow automatically?
Fingertip doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Fingertip
$100 in credits. No card required. Connect in minutes.