with Wordpress.com and TidyCal?
Triggered when an existing appointment is cancelled by a client or by the owner. See the documentation
Emit new event for each new comment added since the last run. If no new comments, emit nothing.
Emit new event for each new follower that subscribes to the site.
Emit new event for each new post published since the last run. If no new posts, emit nothing.
Triggered when a new appointment is booked using TidyCal. See the documentation
The Wordpress.com API empowers developers to extend and integrate their website's capabilities with custom automations and connections to a multitude of apps. Through Pipedream's serverless platform, you have the ability to automate content management tasks such as posting new articles, managing comments, and synchronizing users. This can streamline content workflows, enhance user engagement, and keep your site's data in sync with other services like social media, email marketing platforms, and analytics tools.
import { axios } from "@pipedream/platform"
export default defineComponent({
props: {
wordpress_com: {
type: "app",
app: "wordpress_com",
}
},
async run({steps, $}) {
return await axios($, {
url: `https://public-api.wordpress.com/rest/v1.1/me`,
headers: {
Authorization: `Bearer ${this.wordpress_com.$auth.oauth_access_token}`,
},
})
},
})
The TidyCal API allows for scheduling automation, linking your calendar to create and manage bookings. In Pipedream, you can harness this API to create event-driven workflows, such as syncing with other calendar services, triggering reminders, or connecting with CRM systems to streamline your scheduling process. Pipedream's serverless platform enables you to build and run these workflows efficiently, without the need to manage infrastructure.
import { axios } from "@pipedream/platform"
export default defineComponent({
props: {
tidycal: {
type: "app",
app: "tidycal",
}
},
async run({steps, $}) {
return await axios($, {
url: `https://tidycal.com/api/me`,
headers: {
Authorization: `Bearer ${this.tidycal.$auth.oauth_access_token}`,
},
})
},
})