iTRON

igortron

This plugin lets you send Contact Form 7 messages to Telegram chats via a bot. Setup takes just a few steps:
<ol>
<li>Create a Telegram bot (<a href="https://core.telegram.org/bots#3-how-do-i-create-a-bot" title="Telegram docs" rel="nofollow ugc">how to</a>).</li>
<li>Create a bot in the plugin UI.</li>
<li>Paste the bot token into the bot form (PHP constants also available).</li>
<li>Create a channel in the plugin UI — it links your Contact Form 7 forms to Telegram chats.</li>
<li>Add users to the subscriber list by sending the <code>/cf7tg_start</code> command to your bot. To add a group, first add the bot to the group, then send <code>/cf7tg_start</code> in that group.</li>
<li>Approve or decline subscription requests on the Contact Form 7 → CF7 Telegram settings page.</li>
<li>Configure the channel: choose which forms to send messages from.</li>
</ol>
<h4>Hooks and constants</h4>
Filter <code>wpcf7tg_skip_tg</code> 
Use it to skip sending a Telegram message.
Filter <code>wpcf7tg_markdown</code> 
Use it to customize the allowed Markdown tags.
This plugin uses <a href="https://core.telegram.org/api" title="Telegram docs" rel="nofollow ugc">API Telegram</a> and sends remote HTTP requests to Telegram servers to deliver notifications.

Message Bridge for Contact Form 7 and Telegram

The best plugin to connect your CF7 form to Telegram. This is a lightweight plugin that also parse your HTML tags into markdown to format well done the output messages. 

Good job! 

A lightweight plugin to connect CF7 to Telegram

After the plugin update, the shortcode used in CF7 forms was removed. As a result, it is now displayed as plain text inside the form.
When releasing such updates, it is important to provide migrations and maintain backward compatibility. If functionality is removed, a fallback or automatic replacement mechanism should be left in place to avoid breaking existing forms.

Shortcode removed without migration

Deliver Contact Form 7 submissions to Telegram instantly via a bot.

When content is deleted in WordPress, the default behavior is to return a 404 (Not Found) status code. However, according to HTTP specifications, a 410 (Gone) status code is more appropriate for resources that have been permanently deleted and will not return.
This plugin automatically returns a 410 status code for: 
 – Deleted posts 
 – Deleted pages 
 – Deleted custom post types 
 – Deleted users 
 – Deleted media attachments
Once activated, the plugin works automatically. When a visitor tries to access a URL that previously contained content but has been deleted or moved to trash, they will receive:
<ul>
<li>A 410 HTTP status code in the response headers</li>
<li>The standard WordPress 404 page template (customizable via your theme)</li>
</ul>
<h3>Related Resources</h3>
<ul>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410" rel="nofollow ugc">HTTP 410 Gone – MDN Web Docs</a></li>
<li><a href="https://tools.ietf.org/html/rfc7231#section-6.5.9" rel="nofollow ugc">RFC 7231 – HTTP Status Codes</a></li>
<li><a href="https://developers.google.com/search/docs/crawling-indexing/http-status-codes" rel="nofollow ugc">Google’s guidelines on 410 vs 404</a></li>
</ul>

Gone Control

A WordPress plugin that ensures HTTP 410 (Gone) status code are returned for deleted posts, pages, and CPT, improving SEO and user experience.

Message Bridge for Contact Form 7 and Telegram vs Gone Control