Myworkingmemory × Zapier

Connect useful API results to your documents and sheets.

Use the public Apify app in Zapier to call our YouTube, Shopify and Email tools. Choose the source and destination that fit your work.

Our public Zapier setup hub links these three APIs to customer-owned Apify access. Directory approval and guided-template links are separate; after selecting accounts, map the source and output fields in your Zap.

From a new row to a useful result

  1. In Zapier, choose a trigger such as Google Sheets → New Spreadsheet Row, then connect your own source.
  2. Add Apify → Run Actor and Fetch Results. Connect your own Apify account, choose Apify Store, and select the exact Myworkingmemory Actor below.
  3. Map the source row to the Actor input. Use one video, one storefront request or one email per row to start. Keep your own provider keys private.
  4. Add a destination action and map the returned fields. A multi-action Zap requires a Zapier plan that permits it. Review all inputs and pricing before testing; a real test starts a real Actor.

Your Apify account pays for Actor usage. Zapier and, for Email, MillionVerifier costs are separate. The Apify action’s output Limit controls returned dataset rows, not work performed or billed Actor events.

Choose your API

YouTube captions → a Google Doc

Actor: myworkingmemory~wicked-youtube-transcript-scraper-api

Map the source video URL to videoUrl, choose targetLanguage, and keep listOnly:false. In Google Docs → Create Document From Text, map the returned title to the document title and URL, language and text to its contents.

Uses existing captions, not audio transcription or translation. Inspect missing-caption results instead of creating a document with invented text.

Shopify snapshot → spreadsheet rows

Actor: myworkingmemory~shopify-store-extractor

Provide the public storefront in startUrls. Start with ten products and keep paid extras disabled. Map title, URL, currency, minimum and maximum price, availability, variant count and capture time into separate sheet columns using Create Multiple Spreadsheet Rows.

Retain the coverage report. A capped snapshot is not a full catalogue and public availability is not stock quantity.

Email verification → a reviewed source row

Actor: myworkingmemory~email-verifier-bulk

Map one source email into emails. Enter your own MillionVerifier key in the Actor’s private password field mv_api_key. Update the original source row with result, quality, safe_to_send, reason and is_test; preserve its row ID.

The shared pilot is exhausted. New real-address checks require your MillionVerifier key and credits. Do not send mail; uncertain or test results need review.

Keep the output honest

Inspect the Actor’s returned status and coverage before using a result. A successful run with missing captions, incomplete product coverage or an uncertain email verdict does not supply a complete result. Preserve source URLs and capture times so the next step can use the result correctly.

For a simple one-action Zap, the returned data remains in Zap history and the Apify dataset. Add the document or spreadsheet action when you want delivery to that destination.

Apify’s Zapier guide ↗ · Apify integration and events ↗

Use a blank sheet and a short checklist

Get header-only source CSVs for your own data, per-API setup checklists and labelled synthetic result previews. The YouTube sheet is an alternative input queue; a channel trigger can be used instead. Shopify URLs can also be entered directly into the Actor’s configuration.

These files contain no credentials or customer records. Synthetic previews are examples, not returned API results. Your keys remain in private platform connection fields.

Need help connecting?

Contact dean@myworkingmemory.ai with the Actor, Zap step and a redacted error. Do not send credentials, provider keys or private contact lists.