Gmail
Connect a mailbox with Google sign-in. Send from your own address, and replies are filed against the right contact and deal automatically — so the thread is complete without anyone copying it across.
IMAP and SMTP
Any standards-compliant mail host. The same send-and-file behaviour as Gmail, for teams not on Google.
Outbound webhooks
Signed HTTP callbacks when a lead arrives or a deal changes stage. Three retries with exponential backoff, and an id you can de-duplicate on.
Documentation →REST API
A versioned, token-authed API over the same data the interface uses. Scoped per token, OpenAPI 3.1 document published.
Documentation →Your AI provider
Anthropic, OpenAI, Google Gemini or xAI — your key, your account, your rates. Used for enrichment, reply drafting and message composition. Add more than one and switch whenever.
Google Places
Business search and address data, billed to your own Places key rather than resold through us.
SMS
Two-way text messaging with opt-out handling, delivered through Twilio. Conversations land in the same timeline as email.
Payments
Invoicing and payment collection against a deal, so the money is part of the record rather than a separate system to reconcile.
Inventory systems
A connected inventory application can push item snapshots in and post leads back out, keeping the CRM authoritative for customers without owning the catalogue.
Bring your own credentials
The AI and Google Places connections work differently from most integrations you will have set up elsewhere: you supply the key, and the work bills to your provider account at your rates and under your quota. FullArc holds no platform key for either.
That is a worse signup experience and a better arrangement. You pick the provider and the model. You see the real cost rather than a marked-up allowance. Your prompts go to a vendor you have your own agreement with. And nothing you depend on rests on a contract between us and a third party that you never read.
Keys are encrypted at rest, used only for your account's requests, and never returned to the browser once saved — see Security.
Build your own
Anything the interface can do, a script can do. If the integration you want is not on this page, it is usually a short job against the API rather than a feature request:
- REST API — businesses, contacts, leads, transactional email and drip enrolment.
- Webhooks — push changes into your systems as they happen instead of polling for them.
- OpenAPI 3.1 document — public, no token needed. Generate a client from it.
Tell us what you are connecting and why at hello@getfullarc.com. Knowing which integrations people actually need is how they get built — and often the API already covers it, in which case we will show you how.