Twitter Evernote Integration Ended: 5 Fixes That Work

The Twitter Evernote integration is dead, and no amount of reconnecting accounts will revive it. The honest conclusion, up front: you are not looking at a sync bug, you are looking at two companies that both changed their terms, and the fix is a manual capture habit that takes about five seconds per post. Most of the automation advice still floating around for this problem was written before 2023 and quietly stopped being true.

Below is what actually broke, why the usual workarounds went silent instead of erroring, and five replacement routes judged on the only things that matter: time to captured, whether you can find it again in six months, whether it produces a next action, and what survives an export.

Why the Twitter Evernote integration stopped working

Three separate things failed, at different times, in a way that makes it look like one mysterious outage.

Evernote retired its Twitter capture account, the one where you sent a tweet to @myEN and it landed in your default notebook. That path has not existed for years. If you still have a note somewhere describing how to link your Twitter account inside Evernote’s settings, that note is a museum piece.

Then came the X API changes of 2023. Free read access went away. IFTTT withdrew its Twitter triggers as a direct result, and a large number of Zapier recipes simply stopped returning data. Here is the part that catches people: an applet that cannot read anything does not shout. It just runs and finds nothing. Most people discovered the problem weeks later, at a weekly review, when the notebook they had been trusting was empty and they could not work out how long it had been empty for.

Evernote’s own terms moved as much as X’s. Under Bending Spoons the free plan now caps you at 50 notes in a single notebook, and email-to-note sits behind a paid plan. Check the current plan comparison before you design anything, because these limits have changed more than once. A firehose of liked posts would eat a free account’s entire allowance inside a fortnight.

Confirm your own setup is dead in two minutes

• Open your automation tool’s activity or history log and look at the last successful run that actually created a note. If the last real note predates mid-2023, it is the API, not sync.
• Check whether the Twitter or X service still appears in the tool’s trigger list at all. In IFTTT it does not.
• Send one manual test: email a note to your Evernote address. If that bounces or silently fails, you are on a plan without email-to-note.
• Search your target notebook for anything created this month. Empty notebook, working app, no error message: that is the signature of a withdrawn API, not a broken device.

Decide what a saved post actually is before you rebuild anything

Before choosing a replacement, clarify in the GTD sense. A saved post is one of three things. Most of them are reference material, worth keeping only if you would plausibly search for it later. A few are someday/maybe, interesting ideas with no commitment attached. A small handful hide a real next action, something like “Email supplier about the pricing change mentioned in that thread”.

A bookmark is an undecided open loop. You have not decided anything, you have just deferred the decision and told yourself you will deal with it later. The loop closes when you write the action in your own words, not when you tap the save icon.

And the one-inbox rule matters here more than anywhere. Run X bookmarks, X likes and an auto-filling Evernote notebook at the same time and you have three parallel inboxes, none of which gets emptied. Pick one staging area. Process it to zero.

The test I use before saving anything: if I could not find this again, would I actually miss it? Nine times out of ten the honest answer is no, and the right move is to read it now and let it go. A typical week for me produces 30 to 50 saves, of which perhaps five earn a note and one or two contain a genuine commitment. Automation that captured all 50 would bury those two.

Fix 1: share sheet straight into Evernote or your notes app

The replacement for the Twitter Evernote integration that nobody wants to hear, because it is manual, and it is also the one that works.

On iPhone and iPad: tap the share icon on the post, choose your notes app, and before you save, paste the post text and the author’s handle into the note body. On the Mac, copy the text, then use your notes app’s clipper or global capture shortcut. Add one tag. Not four. One, so that future-you has a single reliable filter.

Save the words, not just the link. Accounts go private, posts get deleted, quote tweets lose their parent, and link previews stop resolving. A notebook full of bare URLs becomes a notebook full of dead ends, usually around the time you finally need one of them. Text first, author second, link third as a secondary reference.

Time to captured: a few seconds. Set that against the hours you would spend building, debugging and re-authorising an automation that one API pricing change can kill. Where it falls down is long threads, which arrive as a single top-post link, and image-heavy posts where the point is in a screenshot. For those, take the screenshot yourself and attach it, or use fix 4.

Fix 2: use X bookmarks as a staging area, swept weekly

Bookmarks and bookmark folders are fine as a holding pen. They are not an archive, because they live outside your trusted system, inside an app whose search you do not control and whose export options are limited.

Build a five-minute sweep into your weekly review. Open bookmarks, work top to bottom, and for each one decide: note it, action it, or delete it. The aim is zero by the end. In practice, out of 30 to 50 saves you will keep a handful and bin the rest without regret, which tells you something useful about how much of this material was ever worth storing.

The trap is obvious once stated. Skip the sweep twice and bookmarks become the fourth list you never open, which is exactly the state you were in when the old integration died and you did not notice for a month.

Fix 3: your own X API access, and what it really costs

Zapier and Make can still talk to X, but only through paid developer access, and the read volumes that matter sit on the higher tiers. Look at the X developer product tiers yourself before planning anything, because the pricing and the limits have been revised repeatedly since 2023. The free tier is built around posting, not reading.

There is a defensible case for paying: monitoring a brand account, a client’s mentions, or a competitor set where the output feeds actual work. For piping your own likes into a personal notebook, the monthly bill tends to dwarf what you pay for your notes app and your task manager combined. That is absurd for the job it does.

If you do build it, build a canary. Have the scenario write one dated test note every Sunday, and put “check canary note exists”on your weekly review checklist. Silent failure is the real risk with any API-dependent capture route, and a missing dated note is a two-second check.

The cheaper middle ground: email-to-note on a paid Evernote plan, triggered by you. Share the post, choose Mail, send it to your Evernote address with a subject line you would actually search for. Slower than automation, immune to API changes.

Fix 4: a read-later layer between X and your notes

Route posts and threads into a read-later app, read them properly there, highlight the two sentences that matter, and export only the highlights into your notes. Your notebook then holds things you chose, not everything you tapped.

Retrieval is the job this protects. Two thousand auto-saved posts make every future search noisier; a hundred deliberately clipped ones stay useful. Manual capture is slower per item and better per search, and search is what you are paying a notes app for.

Before subscribing, check two things. First, the maths: read-later and highlight tools generally carry a monthly subscription of their own, so check the current pricing and compare it with what you already pay for notes and tasks, since this is a third subscription doing a job the first two partly cover. Second, the export. Ask whether highlights come out as plain text or Markdown, and whether each highlight carries its source link with it. If the answer is “sync to our partner app only”, that is an exit cost dressed up as a feature.

Fix 5: send the few that matter to your task manager instead

When a post implies something you have to do, it does not belong in a notebook at all. Send it to Drafts, Todoist, Things or OmniFocus, and write the action as a verb plus a context: “Email Sam re: supplier pricing change (@computer)”, with the post text pasted into the note field. A link alone is not a next action. It is a reminder to make a decision you have already avoided twice.

An AI assistant is genuinely good at one part of this: turning a vague save into a clear verb phrase, or summarising a 40-post thread down to the three claims you cared about. It is bad at deciding what matters to you. It will invent deadlines, assume urgency and flatten your priorities, which is why I treat it as a clarifying assistant rather than a decision-maker. If you use ChatGPT Pages, canvas or whatever shareable document feature your assistant currently offers (these change often, so check what your plan includes), it works well as a project support note for one research thread, holding the raw material while the single next action lives in your task manager.

That separation is what keeps your daily review sane. The question at the start of the day is not “what did I save”, it is what you can realistically do now, here, with this energy, which is the same decision process covered in the guide to how to prioritise tasks in a GTD system. Posts that became actions compete fairly with everything else. Posts that became reference stay quiet until you search for them.

Which route fits your setup, and is Evernote still the destination?

Short decision path. Under ten saves a week and you only need them occasionally: fix 1, share sheet, done. Thirty or more a week and you read long threads: fix 4 feeding fix 1. Posts that mostly create work rather than reference: fix 5, straight to the task manager. A client or brand to monitor and a budget: fix 3, with a canary. Nobody needs all five.

On whether Evernote stays the home for it, three signals say move the archive. You keep hitting the free tier’s 50-note wall. The pricing has changed again and the number no longer matches what you get. Or, the quiet one, you have never actually tested an export, which means you do not know what you own.

An ENEX export keeps your note text, attachments, tags and created and updated timestamps, which covers most of what matters for saved posts. What tends to degrade is note-to-note links, saved searches, reminders and fiddly table formatting. Migrate in this order: export one small notebook, import it into the target app, check that tags, dates and attachments survived, then do the rest, keep the ENEX files backed up somewhere outside both apps, and do not cancel the old subscription until you have searched for something old and found it.

If you are at that point, the next thing to read is the comparison of note-taking apps judged on capture, retrieval, reference storage, export and feeding next actions, and the breakdown of Evernote alternatives with their real migration costs if you have decided the notebook is moving. The old twitter evernote integration is not coming back, but losing it costs you about five seconds a post, which is cheaper than the automation ever was.

Frequently Asked Questions

Does the Twitter Evernote integration still work?

No. Evernote retired its Twitter capture account years ago, and the X API changes of 2023 removed the free read access that third-party workarounds depended on. Nothing in Evernote’s settings will restore it, and reconnecting accounts will not help. Capture now has to go through the share sheet, a read-later app, email-to-note on a paid plan, or your own paid API access.

What happened to Evernote’s @myEN Twitter account?

It was the official address you sent or mentioned a tweet to in order to have it saved to your Evernote account, and Evernote discontinued it. Any guide still describing that workflow was written before the feature was withdrawn. There is no direct successor inside Evernote.

Can I still send posts from X to Evernote by email?

Yes, but only if your Evernote plan includes email-to-note, which sits behind a paid tier at the time of writing. Use the share sheet on the post, choose Mail, and send it to your Evernote address with a searchable subject line. Paste the post text into the body rather than relying on the link alone.

Are IFTTT or Zapier usable replacements for saving tweets to Evernote?

IFTTT withdrew its Twitter triggers after free API read access ended, so no. Zapier and Make can still connect to X, but only via paid developer tiers whose cost usually exceeds what a personal notes subscription is worth. If you do build something, add a weekly test note so you spot silent failures.

Should saved posts go into my notes app or straight into my task manager?

Reference goes to notes, commitments go to the task manager. If the post implies something you must do, write it as a verb with a context and send it to Todoist, Things, Drafts or OmniFocus with the text attached. Everything else is reference, and should only earn a note if you would genuinely search for it later.