Google Contacts
Access and organize contact listings.
What it does
Reads and writes the contacts in a Google account. Useful when a business's customer list genuinely lives in Contacts rather than in a CRM — which is more common than it sounds.
What you need
An account with Google Contacts that you are entitled to authorise, and a moment in a browser. You do not need an API key: connecting sends you to Google Contacts's own sign-in and consent screen, and what comes back is an authorisation rather than a password. RAiN never sees your password, and the authorisation is held by our integration provider on our instructions — see the Integrations & Connected Accounts notice for what that means.
Connecting it
Connections belong to one project. A system built for one client never acts on another client's account, and a package handed to a business runs on theirs — so the same integration is connected again, separately, for each project that needs it.
- Open the project and stay on the Visual Editor tab.
- Open the Tools & Integrations rail on the right.
- Find Google Contacts and press Connect.
- Authorise in the window that opens, then come back. The rail will show it as connected.
The consent link is good for about twenty minutes. If you leave it and come back tomorrow, press Connect again rather than reusing the old tab.
To stop it, press Disconnect. That ends this project's access immediately. You can also revoke it from Google Contacts's own security settings, which works even if you never open RAiN again.
What an agent can do with it
1 actions are available once connected. Not connectable yet — see below. They appear in the tool list for this project only — a project that has not connected Google Contacts is never offered them.
| Action | What it does |
|---|---|
google_contacts_modify_contact_group_members |
Modify Contact Group Members |
Tick the ones an agent may use, or choose one in an Action step to run it exactly as written with no model involved.
A worked example
A small agency's agent adds every new enquiry to Contacts with a label for its source, so the owner's phone shows who is calling and where they came from.
When it goes wrong
It cannot be connected yet. Google Contacts has no managed authorisation available, so RAiN must register its own application with Google before anyone can connect it. Until then this integration shows as soon.
See also
- Integrations & Connected Accounts — who holds the authorisation
- Action steps — running one action exactly as written
- Sequences — how steps fit together

