---
title: Twilio Autopilot retirement, Workday connections, Monday.com agents, and bug fixes
slug: twilio-autopilot-retirement-workday-connections-mondaycom-agents-and-bug-fixes
description: Learn about the Twilio Autopilot app retirement, new Authorization code connections for Workday, new Google Drive and monday.com modules, and other app updates and fixes.
docTags: 
createdAt: 2026-10-14T08:38:53.378Z
---

Here's a quick look at our app updates this week.

## Twilio Autopilot: app retired

The Twilio Autopilot app is retired in Make. Twilio shut down its Autopilot API in August 2023, so the app no longer works. This change is effective immediately and requires action.

### What's changing?

The Twilio Autopilot app and its modules are now hidden and unavailable in new scenarios.

- Existing scenarios that use Twilio Autopilot modules return an error when they run.
- You can't create new scenarios or connections with this app.
- The twilio-autopilot connection type is also retired.

### What do you need to do?

If you have scenarios that use Twilio Autopilot modules, you will need to remove them. Twilio has not provided a direct replacement for the Autopilot service. You will need to explore alternative solutions depending on your specific use case.

### Retired Modules

The following modules are retired and have no direct replacement:

| Deprecated module | Replacement           |
| ----------------- | --------------------- |
| Create Assistant  | No direct replacement |
| Read Assistant    | No direct replacement |
| Update Assistant  | No direct replacement |
| Delete Assistant  | No direct replacement |
| List Assistants   | No direct replacement |
| Create Task       | No direct replacement |
| Read Task         | No direct replacement |
| Update Task       | No direct replacement |
| Delete Task       | No direct replacement |
| List Tasks        | No direct replacement |
| Create Field      | No direct replacement |
| Read Field        | No direct replacement |
| Delete Field      | No direct replacement |
| List Fields       | No direct replacement |
| Create Sample     | No direct replacement |
| Read Sample       | No direct replacement |
| Update Sample     | No direct replacement |
| Delete Sample     | No direct replacement |
| List Samples      | No direct replacement |
| Make an API Call  | No direct replacement |

***

## Workday Human Capital Management: new Authorization code connection

The Workday HCM app has a new, more secure connection type. Authorize your connection as a specific Workday user so scenarios run with user-specific permissions instead of a generic integration system user.

### New connection type

**Workday HCM (Authorization code)**: Authenticate in your browser using the standard OAuth 2.0 authorization flow. Scenarios run with the permissions of the authorizing user.

### Updated connection type

**Workday HCM (Refresh token)**: The existing OAuth connection that requires a pasted refresh token is renamed for clarity. Its functionality is unchanged, and existing connections continue to work without action.

### Resources

- [Workday Human Capital Management documentation](https://apps.make.com/workday-human-capital-management)

***

## Workday Financial Management: new Authorization code connection

The Workday app has a new connection type that uses the OAuth 2.0 authorization code flow. Individual users authorize Make through their browser, so scenarios run with the permissions of that Workday user and respect your data access policies.

### New connection type

**Workday Financial Management (Authorization code)**: Authorize Make through your browser with the standard OAuth 2.0 authorization code flow. Scenarios only access the data that the user can view in Workday.

### Updated connection type

**Workday Financial Management (Refresh token)**: The existing OAuth 2.0 connection that uses a manually entered refresh token is renamed for clarity. Its functionality is unchanged.

### Resources

- [Workday documentation](https://apps.make.com/workday)

***

## Slack: bot connection support for two modules

The Create a Channel and Invite Users modules in the Slack app now support bot connections. This gives you more flexibility in how you manage your Slack workspace.

### Updated modules

- **Create a Channel**: Supports bot connections in addition to user connections.
- **Invite Users**: Supports bot connections, so you can invite users to channels using either a bot or a user account.

### Resources

- [Slack documentation](https://apps.make.com/slack)

***

## Google Drive: new modules for file metadata and permissions

The Google Drive app has two new modules. Get file and folder metadata without downloading content, and manage access permissions dynamically in your scenarios.

### New modules

- **Get a File/Folder Metadata**: Retrieve details about a file or folder, including its name, parent folders, size, description, custom properties, and web links, without downloading the content. Use it to check or route large files efficiently.
- **List Permissions**: Get a list of users and their access levels for a file or folder. Map the Permission ID to the **Update a File/Folder Access** or **Revoke a File/Folder Access** modules to automate access management.

### Resources

- [Google Drive documentation](https://apps.make.com/google-drive)

***

## monday.com: build AI agents from your scenarios

The monday.com app has a new Agents capability. Build scenarios that act as team members in your monday.com workspace and respond to chats, mentions, and assignments automatically.

### New modules

- **Watch Agent Events (Beta)**: An instant trigger that starts your scenario when your Make agent is activated in monday.com. It supports direct chats, @mentions in item updates, and task assignments.
- **Send Agent Response (Beta)**: Posts a text response to the monday.com chat session where the agent was triggered.

### Updated modules

- **Create an Update**: Now supports replying in threads and mentioning agents, users, or teams.

### How it works

To set up an agent:

1. In monday.com, create a new **Make.com Scenario Agent** to get an Agent API key.
2. In a Make scenario, add the **Watch Agent Events** trigger and create a new **monday.com Agent (beta)** connection using your API key.
3. Build your scenario logic. For example, connect to an AI model like OpenAI, look up customer data in a CRM, or triage tasks.
4. Use **Send Agent Response** or **Create an Update** to send the result back to monday.com.

Your team can now chat with the agent or assign tasks to it in monday.com.

### Resources

- [monday.com documentation](https://apps.make.com/monday)

## monday.com: app name and labels updated

The monday.com app now aligns with its official branding. The app, its connections, and webhooks consistently use the monday.com name, which makes your scenarios clearer to build and maintain.

### What's changed

The following labels now use the monday.com name:

- **Connection labels**
  - Monday v2 is now monday.com.
  - Monday Agent (beta) is now monday.com Agent (beta).
- **Webhook labels**
  - All webhooks that previously started with "Monday" now start with "monday.com". For example, Monday Board's Items is now monday.com Board's Items.

No action is required. Existing connections and scenarios continue to work as before.

### Resources

- [monday.com documentation](https://apps.make.com/monday)

## monday.com: connection validation improved

The monday.com app now validates connections to improve reliability. It prevents the use of agent API keys when you create a connection, so your scenarios run with the correct permissions.

### Connection validation

An issue is resolved where API keys for monday.com agents could be used to create a connection. These agent-level keys have limited permissions and caused scenario runs to fail in certain modules. Make now validates the connection and shows an error if you use an agent API key, so you can use a compatible key from the start.

### Resources

- [monday.com documentation](https://apps.make.com/monday)

***

## Nextcloud: file corruption in Download a file module resolved

An issue that corrupted files, such as .docx documents, in the **Download a file** module is resolved. The module now handles binary data correctly, so later modules in your scenarios can process the files reliably.

***

## Box: issue resolved in Create a Sign Request module

Setting **Text Signatures Enabled** or **Reminders Enabled** to **No** in the **Create a Sign Request** module didn't work as expected. This issue is resolved, and Make now applies these settings when you create a sign request.

***

## PrestaShop: product creation date preserved during updates

The **Update a Product** module no longer changes a product's creation date to the current date. It now preserves the original creation date when you update a product.

***

## EspoCRM: webhook trigger and Delete a Lead fixes

Two EspoCRM issues are resolved. The `Watch Changes` webhook trigger no longer fails silently for some updates, so webhooks from all supported EspoCRM versions, including older self-hosted instances, process correctly. The **Lead ID** dropdown in the **Delete a Lead** module now loads its options.

***

## Zoho CRM: fields restored in Upsert a Lead module

An issue that caused the Description (multiline) and custom Details (rich text) fields to go missing in the **Upsert a Lead** module is resolved. These fields are now available for mapping.

***

## Calendly: updated logo

The Calendly app now uses Calendly's latest logo. This visual change doesn't affect the app's functionality.

### Resources

- [Calendly documentation](https://apps.make.com/calendly)

***

## Basecamp 3: app logo updated

The Basecamp 3 app has an updated logo that reflects its current branding. This visual update makes it easier to identify the app when you build your scenarios.

### Resources

- [Basecamp 3 documentation](https://apps.make.com/basecamp-3)

***

## Tadabase: Bug fixes

We've resolved an issue in the Tadabase app.

- **Update a Record module:** Fixed an issue in the `Update a Record` module where scenarios would fail if a File field contained more than one file. You can now correctly update records with multiple files in a single field. Additionally, the mod
- **Create a Record module:** An issue that caused scenarios to fail with an error when uploading files has been resolved. The module now correctly creates records with mapped files. Additionally, you can now upload multiple files to fields of the 'Files' type
