Know the account before the call
See what your own systems record about a customer, like active projects or usage, before you follow up on a deal.
Go Fig reads customer and usage records from your PostgreSQL database so your brief shows what is happening in each account before you reach out.
This one is for your data team. They connect it once with a solutions engineer, and your brief can use it. Your data stays in your PostgreSQL. Go Fig reads it there and doesn't copy it into its own storage. The connection is read only, and we recommend a read-only user so nothing in the database can change. What your own systems know about a customer can then sit next to the deal you are working.
See what your own systems record about a customer, like active projects or usage, before you follow up on a deal.
Check how a customer has been using what they bought before you reach out about a renewal.
Follow a newly closed customer's first weeks from the records in your database, so onboarding doesn't stall quietly.
In PostgreSQL, your data team creates a user for Go Fig and grants it permission to read only the tables and views it should see (it can look but never change anything).
Go Fig connects to the host and port you give it. If a firewall sits in front of the database, your data team works through what to allow with your solutions engineer.
Add the host, port, database name, username, password, and SSL mode (whether the connection is encrypted) in Go Fig.
Confirm Go Fig can see the tables you expect. From then on, Go Fig reads them in PostgreSQL each time they are used.
No. This one is for your data team. They connect it once with a solutions engineer, and your brief can use it from then on.
Your data stays in your PostgreSQL. Go Fig reads it there and doesn't copy your tables into its own storage. So it can find the right table, it keeps field names, descriptions, and a few sample rows in its search index, as our security page explains.
Go Fig reads the data where it sits each time it is used, so it is as current as your database.
No. The connection is read only. We recommend giving Go Fig a read-only user too, so the database itself makes sure nothing can change.
The host, port, database name, a username and password, and the SSL mode, which sets whether the connection is encrypted.
A solutions engineer connects it with you on the call. Then you see Go Fig work on your own data.