-
-
Notifications
You must be signed in to change notification settings - Fork 12
Actions
James edited this page Aug 15, 2026
·
4 revisions
Actions are what can be performed as certain times of the upload process but not directly affect it.
Specify what actions you want to perform when the upload completes.
- Triggers: Choose what triggers the action to execute.
- When To Execute: Choose what the condition is for the action to execute.
- Always
- Never
- IfSuccessful
- IfFailed
Add an uploaded Apple build to one or more TestFlight beta groups.
- API Key: Which App Store Connect API Key to authenticate with.
- App: Which App Store Connect app the beta groups belong to.
- Beta Groups: Which TestFlight beta groups to add the build to.
- Build ID Format: Format string that resolves to the App Store Connect Build resource ID. Defaults to {appleBuildId} which is populated when uploading a build to TestFlight.
Use a bot to send a message to a channel on a discord server.
- App: Which App/Bot will be sending the message
- Channel: What channel in the Discord server to send the message to
- Server: What Discord server to send the message to
- Text: What text to send
-
Embeds: A list of embeds to send with the message. This is optional and can be used to format the message nicely.
- Color: The color of the embed in hexidecimal. This is optional.
- Description: The description of the embed. This is optional.
- Title: The title of the embed. This is optional.
Send an email via SMTP using one of the accounts configured under Build Uploader -> Services -> Email.
- Account: Which configured SMTP account will be sending the email.
- To: Recipient email address. Supports string formatting.
- Subject: Subject line of the email. Supports string formatting.
- Body: Body of the email. Supports string formatting.
- CC: Optional list of CC recipient email addresses. Each entry supports string formatting.
- BCC: Optional list of BCC recipient email addresses. Each entry supports string formatting.
- Attachments: Optional list of file paths to attach to the email. Each path supports string formatting so tokens like {sourceFile} resolve at send time.
Tag the commit the project is currently on, optionally pushing the tag to the remote.
- Tag: The name of the tag to create. eg: #420 or v1.4.2
- Auto Push: If true, the tag is pushed to the remote as soon as it is created.
- Remote: When pushing tag to git, this is the remote that is used.
Send a message to a Google Chat space using an incoming webhook.
- Space: Which Google Chat space to send the message to. Webhook URL is configured in Preferences.
- Text: What text to send. Supports {keys} like {version}, {taskStatus} and {googleDriveFolderName}.
- ResponseFormatName: If a format key name is provided, the resource name of the sent message is stored under this key so later actions can reference it. eg: GoogleChatMessageName (no curly braces).
Sends a notification about a Nintendo build upload to the team's internal webhook.
- Title: Which Nintendo Title the notification is about.
- Branch: Optional: Which release Branch the notification is about.
- Text: Message text to include in the notification.
- Description Format: Build description that is included alongside the notification payload.
- ResponseFormatName: If provided, the message ID returned by the notification webhook is exposed as this format key for later actions.
Use a bot to send a message to a channel on a Slack server.
- App: Which App/Bot will be sending the message
- Server: What server to send the message to
- Channel: What channel in the server to send the message to
- Text: What text to send
- Attachments: A list of attached messages with the message. This is optional and can be used to format the message nicely.
- ResponseFormatName: When sending a Slack message we receive a Timestamp of that message. If a formatName is provided then that TS is saved as a string format to be used elsewhere in the Upload Task. eg: editing it as a post action.
Use a bot to send a message to a channel on a Slack server.
- App: Which App/Bot will be sending the message
- Server: What server to send the message to
- Channel: What channel in the server to send the message to
- Text: What text to update it to
- Attachments: A list of attached messages with the message. This is optional and can be used to format the message nicely.
- Message Timestamp: The TimeStamp of the message we want to update.