-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1471 from codatio/83239-sdk-property-names
Added product updates
- Loading branch information
Showing
5 changed files
with
94 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
--- | ||
title: "New company update endpoint" | ||
date: "2025-01-09" | ||
tags: ["Product", "Update"] | ||
hide_table_of_contents: true | ||
authors: dcoplowe | ||
--- | ||
|
||
We have introduced a new [Update company](/platform-api#/operations/update-company) endpoint that uses the `PATCH` method to update specific company properties without impacting others. | ||
|
||
<!--truncate--> | ||
|
||
## What's new? | ||
|
||
You can now use our new [Update company](/platform-api#/operations/update-company) endpoint to update one or more company properties without overwriting properties not included in your request. To differentiate it, we have also renamed our existing endpoint that uses the `PUT` method and overwrites all company values to [Replace company](/platform-api#/operations/replace-company). | ||
|
||
For most scenarios where you are currently using the existing [Replace company](/platform-api#/operations/replace-company) endpoint, we recommend switching to [Update company](/platform-api#/operations/update-company) to enjoy greater flexibility and precision when updating company details. | ||
|
||
## Who is this relevant for? | ||
|
||
This feature is ideal for users who need to make partial updates to a company's details without impacting the entire company record. | ||
|
||
## How to get started? | ||
|
||
You can start using the new [Update company](/platform-api#/operations/update-company) endpoint immediately in one of the following ways: | ||
|
||
- **Start using our [client libraries](/get-started/libraries)** for quicker implementation and reduced maintenance. | ||
- If using our libraries, **update them to the latest version**, and the `update` method will automatically use the `PATCH` endpoint. | ||
- **Review our [API reference](/platform-api#/operations/update-company)** with detailed examples and usage guidelines to ensure a seamless integration. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
--- | ||
title: "Zapier app 2.0 released" | ||
date: "2025-01-10" | ||
tags: ["Product", "Update"] | ||
hide_table_of_contents: true | ||
authors: dcoplowe | ||
--- | ||
|
||
We’re excited to announce that we've upgraded our Zapier integration to support our latest [webhook event types](/using-the-api/webhooks/event-types), making it even easier to automate your workflows. | ||
|
||
<!--truncate--> | ||
|
||
## What's new? | ||
|
||
We've published a new version of our Zapier app. With version 2.0, you can: | ||
|
||
- **Subscribe to our latest event types** using the newest available triggers. | ||
- **Create multiple subscriptions** to listen to one or more event types at the same time. | ||
- **Use the updated webhook schema** for seamless integration. | ||
|
||
![Zapier event type selection screen](/img/updates/250108-zapier-integration-v2.png) | ||
|
||
## Who is this relevant for? | ||
|
||
This is relevant for anyone looking to automate their workflows using Zapier's no-code platform and clients who are using version 1.0 of our Zapier app. | ||
|
||
Zapier enables you to connect applications and automate tasks by setting up rules that define how data flows between tools and services. With the Codat Zapier app, all [Codat webhooks](/using-the-api/webhooks/event-types) are available as *triggers*. This makes it possible to build workflows you need without writing any code. | ||
|
||
For example, here’s how you can use Zapier with Codat: | ||
- **Real-time notifications:** send a Slack message or an email when a new company shares data with you. | ||
- **Error tracking:** post an alert when a sync error occurs to ensure quick resolution. | ||
- **Data management:** automatically add onboarded companies to a spreadsheet. | ||
|
||
## How to get started? | ||
|
||
To start building your own workflows, you need **a Zapier account** and **Admin or Developer** access to your Codat instance. See how to [create a Zapier workflow](/using-the-api/webhooks/zapier-integration#create-your-workflow) using the Codat app. | ||
|
||
If you already have a Zapier automation built with our version 1.0 app, see how you can [update your existing Zaps](/updates/250109-deprecation-zapier-integration-v1#action-required) to use version 2.0. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
title: "2025-04-10: Deprecation of Zapier app version 1.0" | ||
date: "2025-01-10" | ||
tags: ["Deprecation", "Webhooks"] | ||
authors: dcoplowe | ||
--- | ||
|
||
Following the [release of version 2.0](/updates/250108-zapier-integration-v2) of our Zapier app, we will deprecate version 1.0 on **April 10, 2025**. | ||
|
||
<!--truncate--> | ||
|
||
## Action required | ||
|
||
We have released a new version of our Zapier app that supports our latest webhook [event types](/using-the-api/webhooks/event-types). To ensure uninterrupted service of your workflows, update your existing Zaps to use the latest version of our app. Follow these steps: | ||
|
||
1. Identify your [active Zaps](https://zapier.com/app/assets/zaps) that use version 1.0 of the Codat app. | ||
2. Click the Zap you want to edit, then click **Edit** on the Zap's trigger tile. | ||
3. On the trigger detail screen, click **Setup**, then click **Update** and follow on-screen instructions. | ||
|
||
![Update Zapier app version](/img/updates/250109-deprecation-zapier-integration-v1.gif) | ||
|
||
## Expected impact if no action is taken | ||
|
||
If you don’t update your Zaps by **April 10, 2025**, yur workflows will stop functioning because version 1.0 will no longer receive legacy event types. Ensure your workflows continue without interruption by updating the Zaps today. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.