--- title: "Connect Google Cloud Logging and Pelcro - APIANT.ai" description: "When \"New Log Entry Matching Filter\" fires in Google Cloud Logging, your agent runs \"Create Customer\" in Pelcro." canonical: "https://apiant.ai/connect/google-cloud-logging-to-pelcro" --- # Connect Google Cloud Logging and Pelcro When **New Log Entry Matching Filter** fires in [Google Cloud Logging](https://apiant.ai/connections/google-cloud-logging), your agent runs **Create Customer** in [Pelcro](https://apiant.ai/connections/pelcro), or **Customer Created** in Pelcro to **Write Log Entry** in Google Cloud Logging. Describe the whole flow and it is built, tested on every scenario and kept running. Google Cloud Logging **1** trigger Google Cloud Logging **3** actions Pelcro **5** triggers Pelcro **12** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Google Cloud Logging and Pelcro to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What Google Cloud Logging and Pelcro can do together ### From Google Cloud Logging to Pelcro - When **New Log Entry Matching Filter** in Google Cloud Logging then **Create Customer** in Pelcro - When **New Log Entry Matching Filter** in Google Cloud Logging then **Update customer** in Pelcro ### From Pelcro to Google Cloud Logging - When **Customer Created** in Pelcro then **Write Log Entry** in Google Cloud Logging - When **Customer Updated** in Pelcro then **List Log Entries** in Google Cloud Logging Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with Google Cloud Logging and Pelcro ## Triggers and actions 6 triggers · 15 actions - Trigger **New Log Entry Matching Filter** Triggers when a new log entry matching a Cloud Logging filter is written to a project. - Action **List Log Entries** Returns log entries from a project that match a Cloud Logging filter, newest first. - Action **List Logs** Returns the names of the logs in a project that have entries. - Action **Write Log Entry** Writes a log entry to a Cloud Logging log in a project. - Trigger **Customer Created** Triggers when a user registers via the Pelcro Platform. This means that a customer record exists in Pelcro and has a unique email address, password, and customer ID associated to it. - Trigger **Customer Updated** Triggers when a customer is updated in Pelcro. - Trigger **Newsletter Created** Triggers when a new newsletter subscription is created in Pelcro. - Trigger **Newsletter Updated** Triggers when an existing Pelcro newsletter subscription is updated, such as a change to the subscriber's mailing lists or consent. - Trigger **Subscription Created** Triggers when a new subscription is created in Pelcro. - Action **Add address** Creates a new shipping, billing or primary address for a Pelcro customer. - Action **Add coupon** Creates a new discount coupon on your Pelcro site, with either a fixed amount or a percentage off. - Action **Create Customer** Creates a new customer on your Pelcro site. - Action **Create Newsletter** Creates a newsletter subscriber in Pelcro with their email, signup source and optional consent details. - Action **Create Plan** Creates a new pricing plan under a Pelcro product, setting its price, currency, billing interval and subscription behavior. - Action **Create Product** Creates a product in your Pelcro site. Plans and their prices are added under a product. - Action **Create Subscription** Creates a subscription for a Pelcro customer on a plan, optionally with a coupon, trial period or gift details. - Action **Get coupon** Returns a single coupon by id, including its code, discount, duration, redemption count and expiration. - Action **Get newsletter** Returns a single newsletter subscriber by id, including their email, name, lists and consent details. - Action **List newsletters** Returns newsletter subscribers on your Pelcro site, optionally filtered by exact email address. - Action **Update customer** Updates an existing Pelcro customer's profile, such as contact details, marketing preferences, password and metadata. Fields left blank are left unchanged. - Action **Update Newsletter** Updates an existing newsletter subscriber's email, signup source, name, lists and consent details. ## Each app on its own - [ **Google Cloud Logging** Managed service for storing, searching and analyzing log data from Google Cloud and other sources.](https://apiant.ai/connections/google-cloud-logging) - [ **Pelcro** Pelcro is a subscription and membership management platform](https://apiant.ai/connections/pelcro) Reviews ## What our customers say ## More from Google Cloud Logging - [ **Google Cloud Logging to Brazil CNPJ** Query Brazilian companies by CNPJ with full Receita Federal registry data, no key required](https://apiant.ai/connect/google-cloud-logging-to-brazil-cnpj) - [ **Google Cloud Logging to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/google-cloud-logging-to-hubspot) - [ **Google Cloud Logging to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/google-cloud-logging-to-salesforce) - [ **Google Cloud Logging to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/google-cloud-logging-to-slack) - [ **Google Cloud Logging to Google Sheets** Google Sheets](https://apiant.ai/connect/google-cloud-logging-to-google-sheets) - [ **Google Cloud Logging to Google Drive** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-cloud-logging-to-google-drive) ## More into Pelcro - [ **HubSpot to Pelcro** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-pelcro) - [ **Google Sheets to Pelcro** Google Sheets](https://apiant.ai/connect/google-sheets-to-pelcro) - [ **Gmail to Pelcro** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-pelcro) - [ **Google Calendar to Pelcro** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-pelcro) - [ **Google Drive to Pelcro** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-pelcro) - [ **Mailchimp to Pelcro** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-pelcro) Questions ## Google Cloud Logging and Pelcro, answered ### ### What can start an automation from Google Cloud Logging? Any of Google Cloud Logging's 1 trigger in the catalog, including New Log Entry Matching Filter. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Pelcro when something happens in Google Cloud Logging? Any of Pelcro's 12 actions, including Create Customer, Create Newsletter, Create Plan and Create Product. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Pelcro to Google Cloud Logging? Yes. When something happens in Pelcro, your agent can act in Google Cloud Logging too. This page covers both directions: Pelcro's triggers and Google Cloud Logging's actions are listed here as well. ### ### Do I have to build a connector for Google Cloud Logging or Pelcro? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use Google Cloud Logging and Pelcro without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.