Your systems stay. AI Business Profiles connects them.

What goes where?

AI Business Profiles captures the contact before it reaches your systems. From there, things continue where your business already works.

• Appointment: Business Profile → Customer books → Google Calendar or Outlook
• Lead: Business Profile → Enquiry is created → CRM
• Event: New enquiry → Webhook, Zapier or Make → Internal process
• Your own software: Your application → REST API → Leads, appointments, profile

All integrations at a glance.

Every connection with its benefit and how it is connected. Shown is what is built in today. You use external connections once credentials are stored.

Calendar

• Google Calendar (OAuth): Take busy times into account, add bookings.
• Microsoft Outlook (OAuth): Take busy times into account, add bookings.
• Calendar subscription (Subscription address): See appointments in Apple Calendar and other apps.

CRM

• HubSpot (Private app token): Contact and note for each new lead.
• Pipedrive (API token): Person, lead and note for each new lead.
• Salesforce (Org ID): Lead via Web-to-Lead.
• Zoho (Webhook URL): Lead data sent to your Zoho webhook address.

Automation

• Zapier (Webhooks / API): Start workflows from new leads and events.
• Make (Webhooks / API): Start workflows from new leads and events.

Communication & visibility

• Your own SMTP server (SMTP): Send email via your existing mail infrastructure.
• Web push (Browser push): Visitors and guests subscribe to notifications right in the browser – on iPhone after adding to the home screen.
• Google Business Profile (Google Places): Compare your profile details with your Google listing, after setup.

Developers

• Webhooks (HTTPS + signature): Send signed events to your own systems.
• REST API (API key): Read leads, appointments and profile, create leads.

Hotels & restaurants

• Apaleo (hotel PMS) (Client ID + secret): Reservations become stays with a guest link every 30 minutes – read-only, nothing is written back to Apaleo.
• POS interface (API key + webhook): Retrieve orders, report status back, print receipts – with a webhook for every status change. A specific POS provider is connected separately.

Connect appointments directly to your calendar.

Customers book appointments via your Business Profile. A connected calendar ensures that busy times are not offered – and that new bookings end up where you plan your week.

Google Calendar

Take existing appointments into account and add new bookings to your work calendar.

• Connect with your Google account (OAuth)
• Busy times in your primary calendar are hidden when choosing a time
• New bookings are added as events
• Access renews automatically
• Disconnect at any time

Microsoft Outlook

Take busy times from Outlook into account and add booked appointments there.

• Connect with your Microsoft account (OAuth)
• Busy times in your primary calendar are hidden when choosing a time
• New bookings are added as events
• Access renews automatically
• Disconnect at any time

See appointments in other calendars too.

A personal subscription address shows your booked appointments in Apple Calendar and other calendar apps that support subscribing by address.

• Address with a secret key
• Read-only – changes are not sent back
• Archived appointments appear as cancelled
• How often it refreshes is determined by your calendar app

Appointments are entered with a duration of 30 minutes. You can also download the file as a one-off.

The primary calendar of the connected account is used. If the customer cancels via the link in their confirmation, or you cancel in the dashboard, the appointment is removed from your calendar automatically. Rescheduling means cancelling and booking again.

In teams, each staff member can connect their own calendar. Bookings are then made against their availability.

Process leads where your sales team works.

Every new enquiry from your Business Profile can be passed straight to your CRM – once set up, for every new lead, without retyping.

These details are transferred

• Name
• Email
• Phone
• Company
• Interest
• Message
• Source
• Appointment
• Profile link

HubSpot (Private app token)

Bring leads from AI Business Profiles into your HubSpot process as contacts.

• Contact
• Note with the enquiry
• First name, last name, email, phone, company
• If the email already exists, the note is added to the existing contact

Pipedrive (API token)

New enquiries as leads in your Pipedrive inbox – with a person and a note.

• Person
• Lead
• Note with the enquiry
• Name, email, phone
• Lead title from name and interest
• No deal is created

Salesforce (Web-to-Lead (Org ID))

Pass enquiries to Salesforce as leads via its Web-to-Lead method.

• Lead
• Name, email, phone, company, description
• Lead source “AI Business Profiles”
• Web-to-Lead must be enabled in Salesforce

Zoho (Webhook URL)

Send every new lead as structured data to a webhook address from your Zoho environment.

• Data sent to your webhook address
• All lead fields, including time of consent
• You set up further processing in Zoho, e.g. with Zoho Flow

• Transfer in one direction: from AI Business Profiles to the CRM
• Up to six further attempts on temporary errors; you can see the result in the dashboard
• Send a test before real leads come in
• Tokens are stored encrypted and never shown again

If a transfer fails, the lead is kept in AI Business Profiles and resent automatically – up to six times at growing intervals. Not for set-up errors (e.g. a wrong key); you see those in the dashboard right away.

Connect AI Business Profiles to your workflows.

Via Zapier or Make, events from AI Business Profiles can trigger further workflows. You build the workflows themselves in your automation platform.

Zapier – Via webhooks / API

Connect to Zapier via webhooks or the REST API – there is no dedicated Zapier app.

Make – Via webhooks / API

Connect to Make via webhooks or the REST API – there is no dedicated Make app.

• Lead forwarding: Enter a webhook address from Zapier or Make in the dashboard – every new lead arrives there.
• Signed webhooks: For leads, messages, bookings and cancellations, ratings, profile views and vCard downloads – with a signature and delivery log.
• REST API: Retrieve leads and appointments or create new leads.

Example workflows: New lead → Zapier / Make → Create CRM contact, Message the team, Add spreadsheet row, Start email sequence. Examples you set up yourself in Zapier or Make – not included ready-made.

Email via the platform or your own mail server.

Notifications and confirmations are sent via the platform infrastructure or via your own SMTP mail server. This keeps your existing email infrastructure involved.

• Connection is checked before activation
• Password stored encrypted, never shown again
• Test email to yourself from the dashboard

You add your mail server via a setup link that we send you. If it is not set up, the platform sends the emails.

Spot problems early.

In the Delivery section you can see, per channel, what was sent and what was not – with the latest error message and the option to resend. If no sending is set up for a profile at all, the overview points this out.

Send events to your systems automatically.

Webhooks pass relevant events from AI Business Profiles on to your own systems – shortly after they occur, signed and logged.

• lead.created: New enquiry
• appointment.booked: Appointment booked
• vcard.downloaded: Contact saved
• appointment.cancelled: Appointment cancelled
• contact.message: Message via the contact form
• review.submitted: Conversation rated
• profile.viewed: Profile viewed (once per visitor and day)
• restaurant.order.created: New order (with the restaurant module)
• restaurant.order.status_changed: Order status changed – in the dashboard or at the till
• service.request.created: New service request (with the guest guide)

• Separate HTTPS address per webhook
• Choose events per webhook
• Send a test
• Active or paused
• Secret shown once, can be renewed at any time
• Time limit of 10 seconds per delivery

Signed webhooks.

Every message carries a signature. Your system recalculates it using the shared secret, so it knows the message came from you and was not altered in transit.

• HMAC-SHA256 over timestamp and payload
• Timestamp in the signature to guard against replayed messages
• Event, ID and attempt as separate headers
• Verification example in the dashboard

Every delivery in the log.

The delivery log shows every delivery with its event, destination, status code, duration and attempt. In the details you can see the data sent and your system’s response.

Retried automatically. Resent manually.

If your system does not respond, or responds with a temporary error, AI Business Profiles retries the delivery automatically at increasing intervals. After that, you can resend it with one click.

Permanent errors such as 404 are not retried but marked as final immediately. If your system specifies “Retry-After”, this is respected.

Build AI Business Profiles into your own software.

The REST API connects AI Business Profiles with your own applications: retrieve leads, appointments and profile data, create new leads – and, as a POS interface, retrieve restaurant orders and set their status.

• GET /api/v1/leads: Retrieve leads – paginated, filterable by status and date
• POST /api/v1/leads: Create a lead
• GET /api/v1/appointments: Retrieve booked appointments
• GET /api/v1/profile: Retrieve profile data
• GET /api/v1/orders: Retrieve restaurant orders – for your POS, filterable by status and time
• POST /api/v1/orders/:id/status: Set order status, e.g. accepted or ready – the guest is notified
• GET /api/v1/ping: Check connection

Leads created via the API trigger CRM transfer and webhooks just like all other leads. Updating and deleting via the API is not available – except for the status of restaurant orders. Every status change is also reported by the restaurant.order.status_changed webhook.

Create and revoke API keys.

You create keys in the dashboard and give them exactly the permissions an application needs. The full key is only visible when it is created and is stored only as a hash.

• Up to 20 active keys
• Revocation takes effect immediately
• No automatic expiry date – revoke what you no longer need

Access and protection

• Authentication with a bearer key
• Permissions selectable per key
• 120 requests per minute per key
• Each key is valid for your account only
• Clear error codes: 401, 403, 404, 429

API reference in the dashboard

After signing in, you will find endpoints, permissions, error codes and example requests under Integrations & API. There is currently no public documentation.

When a connection needs attention.

Errors do not stay hidden. Every connection shows its latest status in the dashboard – with the appropriate action.

How integrations can work together.

• Appointment: Customer → Business Profile → Booking → Google or Outlook. Take existing appointments into account and add the booking to the work calendar.
• Lead to CRM: QR code → Business Profile → Form or AI → Lead → CRM. The enquiry arrives with its source and message in HubSpot, Pipedrive, Salesforce or, via webhook, in Zoho.
• Webhook: New lead → Signed webhook → Your system. Your own system receives every new enquiry and verifies the signature.
• Automation: New enquiry → Zapier or Make → Your workflow. For example, notify the team and fill in a spreadsheet – set up in your platform.
• Your own software: Your software → REST API → AI Business Profiles. Retrieve leads and appointments, create new leads.

You do not have to replace your existing systems.

AI Business Profiles adds the digital customer contact that comes before your business processes.

• Your calendar stays your calendar.
• Your CRM stays your CRM.
• Your mail server stays your mail server.

Data in and out.

• Leads as CSV: All leads with consent details, for spreadsheets and other systems.
• Contact as vCard: Visitors save your contact details directly to their address book.
• Appointments as .ics: As a subscription address or as a file to download.
• Team from a file: Add staff via a CSV or vCard file, up to 50 at once.
• Team from your website: Import team members from your website and select them.
• Data access request: The data stored for your account as a file.

For custom processes.

For more complex requirements, webhooks, the REST API and your own mail server are available. What you build on them is up to you.

Custom connections to other systems are not included as a development service. Get in touch – we will clarify what is possible with the existing interfaces.

Integrations for White Label too.

A White Label instance runs on the same platform and comes with the same interfaces.

Everything in view in the operator area.

As an operator, you can see webhooks, API keys and deliveries for all customers – without looking at their data.

• Pause or activate webhooks for individual customers
• Revoke API keys
• Resend deliveries that failed permanently
• Send a test event to any address
• Delivery log without content – status and size only
• Every intervention is recorded in the customer’s log

Making data flows traceable.

Data only goes to your own systems (CRM, webhooks, calendar) via connections you set up yourself. The platform’s service providers are listed among the sub-processors; what you connect yourself is listed separately there and appears automatically in your privacy policy as soon as you switch it on.

• Nothing is transferred to your systems before you set up a connection
• Calendar access, CRM tokens, webhook secrets and SMTP password stored encrypted
• API keys stored only as a hash
• Webhooks only to HTTPS addresses, not to internal networks
• Integrations are managed by the account owner; staff can at most connect their own calendar
• Every connection can be disconnected, paused or revoked

Data protection for integrations

Which data protection requirements apply also depends on the connected provider and your configuration. AI Business Profiles provides its own data protection and integration features; for external services, their terms and privacy information also apply.

Frequently asked questions about integrations

Which calendars can I connect?

Google Calendar and Microsoft Outlook directly via your account, once the calendar connection is set up. There is also a subscription address that lets you see your appointments in Apple Calendar and other calendar apps.

Does AI Business Profiles work with Google Calendar?

Yes. Busy times from your primary calendar are hidden when choosing a time, and new bookings are added there. Cancellations via the link or in the dashboard are removed there automatically; rescheduling means cancelling and booking again.

Can I connect Outlook?

Yes, via your Microsoft account – with the same features as Google: busy times are taken into account and new bookings are added.

Which CRM systems are supported?

HubSpot, Pipedrive and Salesforce directly, and Zoho via a webhook address. Once set up, every new lead is transferred – in one direction, into the CRM.

Can I use HubSpot?

Yes. With a private app token, AI Business Profiles creates a contact with a note about the enquiry for every new lead. If the email address already exists, the note is added to the existing contact.

Does AI Business Profiles support Zapier?

Yes, via webhooks and the REST API. There is no dedicated Zapier app. You enter the webhook address from Zapier in the dashboard or use the signed webhooks.

Does AI Business Profiles support Make?

Yes, likewise via webhooks and the REST API. There is no dedicated Make app.

Can I use my own mail server?

Yes. You enter the SMTP server, port, encryption, login details and sender via a setup link from us. The connection is checked before activation and the password is stored encrypted.

Is there an API?

Yes, a REST API for retrieving leads, appointments and profile data and for creating new leads – with the restaurant module also for retrieving orders and setting their status (permissions read:orders and write:orders). You will find the reference with examples in the dashboard.

Can I use webhooks?

Yes, for new leads, messages, booked and cancelled appointments, ratings, profile views and saved contacts. You choose the events per webhook, can send tests and can see every delivery in the log.

Are webhooks signed?

Yes, with HMAC-SHA256 over timestamp and payload. You see the secret once when it is created and can renew it at any time.

Can I resend failed webhooks?

Yes. Temporary errors get up to six delivery attempts automatically. If a delivery has failed permanently, you resend it from the log with one click.

Can I build my own integrations?

Yes, within the scope of the REST API and webhooks. With these, you can connect your own software or platforms for which there is no ready-made connection.

Connect AI Business Profiles to your existing workflow.

Calendar, CRM, email, automations and your own systems – AI Business Profiles fits into your processes instead of replacing them.