> For the complete documentation index, see [llms.txt](https://docs.taskade.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taskade.com/changelog/changelog-2026/july-2026/july-6-2026.md).

# July 6, 2026

{% hint style="info" %}
**Developer highlights.** This section tracks API, MCP, SDK, automation, and Taskade Genesis platform changes for developers. For the full product changelog see [taskade.com/changelog](https://www.taskade.com/changelog); for release newsletters see [taskade.com/blog/updates](https://www.taskade.com/blog/updates).
{% endhint %}

## What's New:

### Relationship Field Type (Phase 1)

Databases gain a **Relationship** field type that links records across projects — think customers ↔ orders or leads ↔ deals. Phase 1 ships the field renderer, configurator, and schema serialization; future phases will add lookup columns and cross-project filtering. See [Projects & Databases](/workspaces/workspaces/projects-databases.md).

***

### Table View Multi-Cell Copy/Paste

Select a **range of cells** in Table View, copy (TSV on the clipboard), and paste into another range — edits are bundled into a single changeset. Works across number, text, select, and date columns.

***

### HTTP Webhook Triggers Now Fire

Automation flows triggered by an incoming HTTP webhook now work correctly by honoring the connection's `authDesc.required` field — no more silent no-ops on webhook-triggered workflows.

***

## Improvements & Fixes:

* Select field values in the Genesis app data gateway now serialize as human-readable labels instead of raw field IDs.
* Duplicate automation node additions are rejected to prevent flow corruption.
* Loop iteration results now persist through execution instead of being discarded between iterations.
* Genesis build errors carry their error taxonomy through to the publish pipeline so causes are visible in published apps.
* General stability, performance, and connector reliability improvements.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.taskade.com/changelog/changelog-2026/july-2026/july-6-2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.