Skip to main content

Similar to this post, I am having a problem with Zapier stripping the @ from Twitter handles,however, in my case I am not autoresponding, it just straight mentioning.
 

When announcing a webcast, I post on WordPress and include the speaker handles in the post title. When this is relayed to twitter the handles get stripped defying the the whole point of the exercise.

 

Example.

Post https://isoc.live/16404/  Tweet 

 

 

I understand that this maybe due to Muskery, but, basically, this means that Zapier is a dead loss. I will disable the zap and do this manually from now on.

 

 

Hi @joly 

Good question.

 

Take note of the Message field description for the Zap action: Twitter - Create Tweet

 

Using Zapier as a Twitter Auto-Responder

A Zap that auto-responds to search mentions is a violation of Twitter's policies for automation.

Twitter’s policy doesn’t allow replies or mentions in response to search mentions. If your Zap has a Search Mention trigger and an action that sends a Tweet to that user’s @username, the Tweet will be posted but the @ will be removed.

Twitter’s policies for automation don't allow @replies in response to search mentions. Here’s a link that discusses Twitter’s policies for using automations with their platform: https://support.twitter.com/articles/76915#replies-mentions.


How come, if I use Jetpack Social, or ‘share’ the WordPress post to Twitter, the handles all show up? Is there a different rule for Zapier?

 

 

 

 

 

 


@joly 

Using automation to post tweets is different than manual interaction that post tweets, and thus is subject to different limitations to prevent abuse.


Here, for instance, are the Jetpack social instructions for auto-sharing to Twitter - https://wordpress.com/support/post-automatically-to-social-media/

A quick read of the Twitter rules above doesn’t clearly prohibit such activity.


@joly 

Different apps have different implementations.

If you are trying to use Zapier to post to Twitter, then those limitations are well documented as it relates to using @mentions.


“. If your Zap has a Search Mention trigger and an action that sends a Tweet to that user’s @username, the Tweet will be posted but the @ will be removed.”

Does not apply.

 

 


@joly 

Take note of the Message field description for the Zap action: Twitter - Create Tweet

 


those limitations are well documented

 

Where?

 

 


@joly 

It mentions the limitation on the field in the Zap Editor.

 

Take note of the Message field description for the Zap action: Twitter - Create Tweet

 

The content of your new tweet. You can truncate text with a Formatter action to meet Twitter's 280 character limit.

Note: In order to comply with Twitter's terms of service, this text will have all @mentions removed.

Read more here: http://zpr.io/6MUuH


If you mean https://help.zapier.com/hc/en-us/articles/8495936186509

 

All it says is “. If your Zap has a Search Mention trigger and an action that sends a Tweet to that user’s @username, the Tweet will be posted but the @ will be removed.”

Does not apply.


@joly

It clearly mentions the limitation on the field description in the Zap Editor.

 

Take note of the Message field description for the Zap action: Twitter - Create Tweet

 

The content of your new tweet. You can truncate text with a Formatter action to meet Twitter's 280 character limit.

Note: In order to comply with Twitter's terms of service, this text will have all @mentions removed.

Read more here: http://zpr.io/6MUuH


@joly 

If you want to take it up with Zapier, you can try opening a ticket with Zapier Support: https://zapier.com/app/get-help


Hey @joly ,

Sorry you’re running into this.

You’re right, this appears to be a bug in the code. At the very least the help text is inconsistent with the actual behavior, in which we remove all mentions regardless of what trigger is on the Zap.

We have an open feature request on this, so I’ll go ahead and add you to that. I don’t know when we’ll address this, but the good news is that since your email address is recorded there, you’ll hear about it as soon as we do.

We also have a main thread open for this issue here, where we’ll be posting any updates as we have them: 

 


Thanks!


Reply