Verbaflo External CRM

We are currently experiencing issues with our Shopify app due to an upstream outage affecting Shopify's services. Multiple Shopify systems are impacted, including Admin, Checkout, Storefront, and Point of Sale. Users may be unable to complete actions that rely on Shopify integrations at this time. We are monitoring the situation closely and will provide updates as more information becomes available. For real-time updates on Shopify's service status, please visit their official status page: https://www.shopifystatus.com We apologize for any disruption this may cause. Once Shopify services are restored, we will work to ensure all affected workflows resume normal operation. Thank you for your patience.

We are currently investigating an issue with Code by Zapier that is resulting in error messages when those steps are running: “Lambda was unable to configure access to your environment variables, because you have reached the grant limit of your KMS key or execution role”. We are working on resolving this as soon as possible, and will update this Status page as soon as possible. If you have any questions, please reach out to our support team — https://zapier.com/app/get-help Thank you for your patience!

We are currently investigating an issue affecting the ability of Code by Zapier steps to run. Starting at approximately 11:00am EST, some Code by Zapier steps began encountering errors, including CodeStorageExceededException OR ResourceConflictException This is affecting new Code by Zapier steps, and some existing steps as well. We will provide updates as we make progress on resolving this issue. Thank you for your patience.

Sidekick users are experiencing an issue with getting logged out, and running into session errors. After the users then log back in, they are no longer able to see and access workspace content and chats. We are currently investigating the cause of this issue, and will update here once we have more information.

We have identified delays between Zap execution and when runs become visible in Zap History. Importantly, Zap executions themselves are not failing or delayed — this issue only impacts the visibility of Zap History data in the UI. Our team is actively investigating the issue and we will continue to provide updates as soon as more information becomes available.

Starting around 1:55 p.m. UTC, Code by Zapier steps have started failing with the error: "No response from child process" Our team is actively investigating and has engaged the owning engineering team.

We are currently experiencing intermittent authentication and connection issues affecting our LinkedIn, LinkedIn Conversions, and LinkedIn Lead Gen Forms integrations. Users may see authentication failures or connection errors when attempting to use Zaps with these LinkedIn integrations. These issues began around 1:50am EDT on May 20th and are impacting a subset of our users. LinkedIn's platform is experiencing widespread API issues, resulting in elevated error rates (primarily 401 authentication failures and 500 server errors). This has been confirmed on LinkedIn's API status page. We are actively monitoring the situation and working with LinkedIn to track their recovery progress. We apologize for any disruption this may cause to your workflows. We'll continue to monitor this closely and will update you as the situation develops.

Our Engineering team is currently monitoring reports indicating that Enterprise users with a high number of app restrictions (over 100) are unable to modify or manage custom actions. Affected users will see the following error when viewing custom actions. We couldn't determine whether this app is restricted. Please try again in a moment. We'll continue to keep our customers informed as we identify the root cause and resolve the issue.

We are currently investigating a spike in errors affecting Facebook Lead Ads integrations. Users may experience failures when running Zaps connected to Facebook Lead Ads, with errors related to missing permissions or unsupported requests. Our integrations team is actively investigating the root cause and working toward a resolution. We will provide updates as soon as we have more information.

We are currently investigating an issue where users may encounter the following error when creating a new connection or reconnecting an app: "Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'. Uh oh, something is not quite right!" Our team is actively working to identify the root cause. We’ll provide updates as soon as more information is available.

We are currently investigating an issue causing elevated latency in hook ingestion and event processing. As a result, some customers may experience delays of approximately 30–40 minutes before events are processed. Our team is actively working on the fix.We appreciate your patience and understanding while we work to resolve this issue.

We are currently investigating an issue impacting Google single sign-on (SSO). Users attempting to log in to their zapier.com account using Google SSO may be unable to authenticate at this time. Impact All users are affected when using Google SSO. Login via username and password remains available, and users with active sessions are not impacted. Running automations continue to operate normally. Current Status Our engineering team is actively investigating the root cause. Initial efforts are focused on reviewing Google SSO configuration, credentials, and related environment variables. Relevant teams have been engaged and are working to identify and resolve the issue as quickly as possible. We will provide further updates as more information becomes available.

We’re investigating an issue affecting some Zaps that use error handling. You may have received an email titled “High Error Ratio” explaining that your Zap would be switched off. In some cases, that may not have matched what you see in normal use, and your Zap may have been paused as a result. We’re working on a fix to prevent this from happening again. If that happened to your Zap, you can turn it back on from your Zapier dashboard. We’ll post another update here when we have more to share.

We are currently investigating an issue where users receive "Session initialization failed" errors when attempting to connect apps in Zapier.

We are looking into an issue related to the Klaviyo app returning 522 timeout errors. This is related to an incident with Klaviyo here: https://status.klaviyo.com/incidents/yyh7s59brj67

Between April 26, 2026, 7:14 PM UTC and April 30, 2026, 4:36 AM UTC, a subset of incoming webhooks to Zapier were not processed during ingestion. Webhooks sent with a Content-Type header that specified a non-UTF-8 character set in the way below were rejected instead of being delivered to your Zaps: Content-Type: application/x-www-form-urlencoded; charset=iso-8859-1 Webhooks using typical UTF-8 Content-Type values were not affected by this issue. If your upstream system sent webhooks matching the pattern above during that time window, those individual events did not trigger your Zaps. Other triggers and webhook formats continued to work as usual. For any specific events that occurred while your app was sending webhooks in that format during the window above, you will need to resend the webhook from the upstream application (for example, by having that app fire the event again or resubmit the payload), so that Zapier receives a new request. Replaying a past run in Zapier does not replace a missing inbound webhook from your app. If you are unsure whether your integration uses that header, check your server or integration configuration for charset=iso-8859-1 (or other non-UTF-8 charset) on application/x-www-form-urlencoded requests to your Zap’s webhook URL.