Step-by-step: How I use IFTTT to send articles from Feedly to Speechify.

As a practitioner deeply invested in workflow automation and API-driven content pipelines, I've found the combination of RSS aggregation and text-to-speech to be a critical productivity multiplier. However, the manual process of transferring articles from a reader like Feedly to Speechify for audio consumption creates a notable friction point. To solve this, I architected an IFTTT applet that functions as a seamless bridge, automating the entire transfer and queuing process. Below is a granular breakdown of the implementation, including the specific triggers, actions, and necessary configuration nuances.

The core logic of the applet is straightforward: when a new article is saved to a designated Feedly board (in my case, "To-Speechify"), IFTTT captures the article's content and pushes it to Speechify's cloud library. The implementation requires careful handling of data formatting to ensure optimal Speechify processing.

**IFTTT Applet Configuration:**

* **Trigger Service:** Feedly
* **Trigger:** "New saved article"
* **Fields:**
* `BoardName`: To-Speechify *(This must match your Feedly board name exactly)*
* **Action Service:** Webhooks (Make a web request)
* **Action:** "Make a web request"
* **Action Fields:**
* **URL:** ` https://api.speechify.com/v1/import`
* **Method:** POST
* **Content Type:** `application/json`
* **Body:** (See the critical JSON structure below)

The pivotal component is the Webhook body, which must conform to Speechify's Import API specification. The Feedly trigger provides several ingredient variables that must be mapped correctly.

```json
{
"url": "{{EntryURL}}",
"title": "{{EntryTitle}}",
"author": "{{EntryAuthor}}",
"source": "Feedly",
"tags": ["automated-import"],
"folder": "IFTTT_Imports"
}
```

**Critical Considerations & Pitfalls:**

* **Content Fidelity:** The `{{EntryURL}}` is the most reliable field. Speechify's API will crawl this URL directly to extract the primary article text. This is superior to using the `{{EntryContent}}` ingredient from Feedly, which often includes truncated or HTML-formatted text that can cause parsing errors in the audio output.
* **Authentication:** The Webhook URL must include your Speechify API key as a Bearer token in the header. IFTTT's Webhook action allows for this via the "Add header" field.
* Header: `Authorization: Bearer YOUR_SPEECHIFY_API_KEY_HERE`
* **Error Handling:** IFTTT provides limited logging. To monitor the pipeline, I recommend a secondary IFTTT applet that logs the Webhook response to a Google Sheet or sends a notification on failure. Check Speechify's API response codes; a `202 Accepted` indicates successful queuing for processing.
* **Rate Limiting:** Be mindful of both IFTTT's execution limits and Speechify's API rate limits if you save a high volume of articles concurrently.

This setup has effectively created a hands-free pipeline for curating audio content. The articles appear in my Speechify library within minutes, categorized under the "IFTTT_Imports" folder, ready for playback. The primary limitation is the dependency on Speechify's URL crawling efficacy; for sites behind paywalls or with complex JavaScript rendering, the import may require a manual fallback process using the direct text import method, which would necessitate a more complex automation involving tools like Zapier or Pipedream for full HTML capture.

—KH