Skip to main content
This guide belongs to the Zapier Twitter integration build.

​
Result handoff

Use Zapier samples and outputFields so later Zap steps map stable values. Use snake_case storage keys when direct API responses use camelCase. Return compact objects from actions and arrays from triggers.

Search tweets action

Return id, tweet_id, text, author_username, created_at, and url. Keep has_next_page and next_cursor when a Zap loops pages.

User profile rows

Return source id as user_id. Keep username, name, followers, verified, and profile_picture. Store the input, has_next_page, and next_cursor separately.

Follower and following rows

Store user_id, username, name, followers, following, verified, and profile_picture. Keep the source account, page cursor, and relationship direction.

Trend rows

Return each trend name, rank, query, and description. Keep response count, woeid, and the selected region with the Zap run.

Tweet or reply write

Send a unique Idempotency-Key. Store id, status, billing, result, and statusUrl. Poll while terminal is false. Retry only when safeToRetry is true, using a new key.

Media attachments

For tweets or replies, pass public URLs in media or uploaded IDs in media_ids. Never send both. For DMs, upload first. Pass 1 media_id in media_ids. Store message_id and leave reply_to_message_id unset.

Monitor and webhook setup

Return monitor id, username, xUserId, eventTypes, isActive, and nextBillingAt. Return webhook id, url, eventTypes, and one-time secret. Map production deliveryId to delivery_id for receiver retry deduplication. Map streamEventId to stream_event_id for event deduplication across webhook changes.

REST hook trigger

Return id, delivery_id, and stream_event_id. Use delivery IDs for endpoint retries. Use event IDs across webhook changes.

Stored event replay

Call GET /events with cursor when a Zap needs replay. Map event and monitor IDs first. Then map occurredAt, hasMore, and nextCursor to snake_case fields.

Receiver acceptance

Zapier controls responses from its generated hook URL. Use a relay when you need custom acceptance or replay rules. Keep signing values, raw bodies, and raw signatures outside Zap history. Keep full headers outside business apps too.

Extraction polling trigger

Return completed job id, toolType, and status. Store normalized IDs, status, has_more, and next_cursor. Then fetch detail rows.
Map friendly region names to WOEID values. Submit the selected value to Xquik.This example shows a search action.

​
Next steps