Integration
Fluidwave + Google Contacts: link people to tasks and email
Bring your Google Contacts into Fluidwave, link people to the tasks and emails they belong to, and @-mention them in notes. Fluidwave writes back only the edits you make, nothing else.
What syncs
| Data | Direction | Notes |
|---|---|---|
| Contact details | Two-way | Names, nickname, job title, organization, birthday, notes, and multiple emails, phones, websites and addresses with Home, Work, Mobile and Other types. Read in full; only edits you make in Fluidwave are written back. |
| Deletions (Fluidwave to Google Contacts) | One-way | Deleting a contact in Fluidwave deletes it in Google Contacts too, after a warning. |
| Account email (Google to Fluidwave) | One-way | Used only to label which connected account a contact came from. |
| Task links, @-mentions and linked task counts (Fluidwave only) | One-way | Stored in Fluidwave and shown on task rows, task detail and kanban cards. Never written to Google Contacts. |
How to set it up
- 1
Open Settings in Fluidwave and choose Connect Google Contacts under Contacts.
- 2
On the Google consent screen, pick the account whose address book you want to use.
- 3
Review the two requested permissions, contacts and userinfo.email, and allow them.
- 4
Wait for the first sync. The Contacts table fills with names, emails, phones, organizations and job titles, with a global search on top.
- 5
Repeat for any other Google accounts; contacts from all of them appear together.
- 6
Open any task, link a contact to it, and start @-mentioning people in notes and comments.
Privacy and permissions
Fluidwave reads the contacts on each Google account you connect so you can search them, link them to tasks and mention them in comments. The sync is two-way, but narrow on purpose: Fluidwave only writes the edits you make in Fluidwave back to Google Contacts, nothing else. Linking a contact to a task, @-mentioning someone, or letting an automation add a contact to a task all stay inside Fluidwave and never touch your Google address book.
Your Google tokens are encrypted with AES before they reach our database. Fluidwave complies with the Google API Services User Data Policy Limited Use requirements. Contact data is never sold and never used for advertising.
Deleting a contact in Fluidwave deletes it in Google Contacts too, and Fluidwave warns you before it does. You can disconnect an account from Settings at any time, and deleting your Fluidwave account removes synced data and encrypted tokens. The integration requests the two scopes below.
| Permission | Why it is needed |
|---|---|
| contacts | Read your contacts and write back the edits you make in Fluidwave, such as a corrected phone number or a new job title. |
| userinfo.email | Identify which Google account each set of contacts belongs to when you connect more than one. |
Features that matter for this
Google Contacts sync
Two-way sync with your address book so contacts can be linked to tasks and mentioned in notes.
Waiting-on tracking
A dedicated status for tasks waiting on a reply, call or message so they stop cluttering your active list.
Visual automation builder
Node-based rules with triggers, conditions and actions across both email and tasks, with live match preview.
What you can do once Google Contacts is connected
Most task managers treat people as a text field. Fluidwave treats them as records you can link, search and act on. After connecting, the Contacts table lists first and last name, email, phone, organization, job title and how many tasks each person is linked to, with a global search across all of it.
Open a contact and you get an inline, autosaving editor for nickname, job title, organization, birthday and notes, plus as many emails, phones, websites and addresses as you need, each typed Home, Work, Mobile or Other. An Open in Google Contacts link jumps to the same record in Google.
The useful part is linking. From a task, link one or more contacts; from a contact, link the tasks they relate to. Linked contacts show on task rows, in task detail and on kanban cards, so “Call Dana about the contract” carries Dana’s number with it. In notes and comments you can @-mention a contact the same way you mention a teammate. Contacts also power email: when you compose in the built-in Gmail client, recipients autosuggest from your address book, and automations can match mail by from contact or recipient contacts. If you keep a waiting-for list, the Waiting status plus a linked contact tells you exactly who you are waiting on.
Automations that use contacts
Contacts appear in the visual automation builder on both sides of the app. Email rules can test from contact and recipient contacts; task rules can test contacts and use Add Contacts and Remove Contacts as actions. Because these match on the linked record rather than a typed name, they keep working when someone emails from a second address you have saved.
Examples that people set up early:
- Client mail becomes client tasks. When an email arrives and from contact is one of your clients → Convert to Task, then Add Contacts with the sender, so the task is already linked to them.
- Investor follow-ups get priority. Task changes, condition contacts includes a specific investor → Set Urgency Important and Add Schedules “Follow-ups.”
- Keep vendor threads out of triage. Email from contact is your accountant → Set Triage Bucket to Task and Add Label “Finance.”
- Waiting-on hygiene. Task status is Waiting and contacts is empty → this is a task you cannot chase; the automation can Set List “Needs a person” so you fix it during your weekly review.
The live preview shows which emails or tasks match before you save, and you can apply the rule to existing items in one click. For people who manage relationships for a living, Fluidwave for sales reps and for executive assistants walk through fuller setups.
Limits and what is not supported
The contacts integration is deliberately narrow, and a few things fall outside it.
- Google Contacts only. There is no support for Apple Contacts, Outlook or Microsoft 365 people, or CSV import of an address book. Contacts have to live in a Google account, personal or Workspace.
- Only your edits are written back. Linking, mentioning and automation actions stay in Fluidwave. If you want a change to reach Google, edit the contact’s own fields in Fluidwave. Nothing else is written.
- Deleting is real. Because a delete in Fluidwave also deletes in Google Contacts, Fluidwave shows a warning first. Unlink a contact from a task instead if you only want it off the task.
- Not a CRM. There are no pipelines, deal stages or activity timelines. What you get is a linked address book inside a task manager, which is enough for most solo operators and small teams and not enough for a sales organization running forecasts.
- Platforms. The macOS desktop app is available; Windows and Linux desktop apps are coming soon. Web, iPhone and Android cover the rest, and the app works offline.
If your contacts are scattered across providers, consolidate them into Google first; the integration then handles multiple Google accounts side by side.
Frequently asked questions
Ready to know exactly what to do next?
Tasks, email, calendar and contacts in one place, with AI that works out what to do next. Free forever, no credit card.