Keep Buildkite failure summaries in Google Drive
Send a Buildkite failure to Notis and keep a clear incident note ready for review.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a File from Text
Creates a new file in google drive from provided text content (up to 10mb), supporting various formats including automatic conversion to google workspace types.
Why this helps
Build failures get buried in notifications, leaving teams to reconstruct what happened later.
- Preserve the failure details in one searchable document.
- Make incident handoff easier.
- Reduce time spent rebuilding context.
Setup
Build it in a few focused steps.
- 1Connect Buildkite and Google Drive once in Notis.
- 2Create an automation in plain language or in Automations, New Automation.
- 3Describe the outcome in one instruction: summarize the Buildkite failure details received and create a Google Drive document.
- 4Pick the Notis webhook trigger and choose where run reports go.
- 5Test with one real failure payload that includes the pipeline, build, and available error details.
Questions about this workflow
Does this start automatically when a Buildkite build fails?
Buildkite trigger events are not available for this workflow. A Notis webhook starts it when an HTTP request sends the failure details.
What if the webhook does not include a cause?
Notis can summarize only the supplied details. The document should identify missing cause information instead of guessing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Buildkite to Google Drive. A trigger fires from one place; an action lands in another.
Buildkite triggers
Google Drive actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add file sharing preference
Modifies sharing permissions for an existing google drive file, granting a specified role to a user, group, domain, or 'anyone'.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Copy file
Duplicates an existing file in google drive, identified by its `file id`.
Create Comment
Tool to create a comment on a file. use when you need to add a new comment to a specific file in google drive.
Create Shared Drive
Tool to create a new shared drive. use when you need to programmatically create a new shared drive for collaboration or storage.
Create File or Folder
Creates a new file or folder with metadata. use to create empty files or folders, or files with content by providing it in the request body (though this action primarily focuses on metadata creation).
Create a File from Text
Creates a new file in google drive from provided text content (up to 10mb), supporting various formats including automatic conversion to google workspace types.
Create a folder
Creates a new folder in google drive, optionally within a parent folder specified by its id or name; if a parent name is provided but not found, the action will fail.
Create Reply
Tool to create a reply to a comment in google drive. use when you need to respond to an existing comment on a file.
Connect any two apps with Notis in the middle.
Buildkite and Google Drive, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Google Drive.