Renewal prep agent is connected to Google Gemini Enterprise through the Zywave MCP and ready to run. That connector is now shared by every other entry in the catalog, so the next one you deploy is a single step.
Caveat. This agent is not published: it is marked Coming soon in the catalog. What you have genuinely set up is the Zywave MCP connector in Google Gemini Enterprise, which is the part that carries over to everything else.
Run it again
Pull my benefits clients renewing in Q4 and assemble their annual notice packets.
If it did not work
- Google Gemini Enterprise says it has no Zywave tools. The connector is not active in that chat. Start a new chat, or re-check step 1.
- You get a sign-in loop. The token expired and no refresh token was issued. Ask your admin whether the client was registered with the
offline_accessscope. - A write is refused, or you are asked to confirm. That is intended. Write tools carry
destructiveHint, so Google Gemini Enterprise asks before it changes anything in Zywave. - Something else. The connection reference is on MCP Apps, including the transport and endpoints your admin will ask about.
Next
- Deploy Prospecting campaign agent in Google Gemini Enterprise: same connector, one step.
- Deploy Book hygiene agent in Google Gemini Enterprise: same connector, one step.
- Browse the rest of the agents catalog.
← Back to the Google Gemini Enterprise setup steps · Renewal prep agent