How to Use the OpenTweet API / Webhook Connector

The API connector is the most flexible connector type. Any system that can send an HTTP POST request can trigger a tweet — your own app, Zapier, Make, n8n, or any custom automation.

How do I set up a tweet template for the API connector?

In the connector settings, define a tweet template with placeholder variables that match keys in your JSON payload. Variables use curly-brace syntax: {product_name}, {price}, {url}. Example template: "Just launched {product_name} at {price}! Check it out: {url}". When a POST request arrives with those keys in the JSON body, OpenTweet substitutes the values and creates the tweet.

How do I integrate with Zapier or Make?

Create an API connector in OpenTweet to get your unique webhook URL. In Zapier, add a "Webhooks by Zapier" action step set to POST. Set the URL to your OpenTweet webhook URL and configure the JSON body to match your template variables. Any Zapier trigger — new email, CRM update, form submission, calendar event — can now fire a tweet. The same process works identically in Make (formerly Integromat) and n8n.

What can I use the webhook connector for?

Popular use cases: tweet new product listings from your e-commerce store, announce uptime recoveries from your monitoring service, share new app reviews from the App Store, tweet form submission milestones from your website, trigger tweets from custom business events in your internal application, or share new job postings automatically.

Can I use the API connector without Zapier?

Yes. Any application that can make HTTP POST requests works. Send a JSON body to your webhook URL with the variables your template expects. No authentication is required on the webhook URL itself (security comes from the URL being unique and private). You can also test it with curl or any API client like Postman.