Integration
Connect Swiftype to Pushbullet
When something happens in Swiftype, your agent does the next thing in Pushbullet. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Swiftype and Pushbullet to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Swiftype and Pushbullet
Triggers and actions 2 triggers ยท 35 actions
Trigger
New DocumentTriggers when a new Document is created.
Action
Add domainAdd a crawler domain to an Engine. POST /api/v1/engines/{engine_id}/domains.json with url.
Action
Add engineCreate a new Engine (index). POST /api/v1/engines.json with name.
Action
Create DocumentCreates a new Document.
Action
Delete documentDelete a document by document_id from a document type. DELETE /api/v1/engines/{engine_id}/document_types/{document_type}/documents/{document_id}.json
Action
Delete domainRemove a crawler domain from an Engine. DELETE /api/v1/engines/{engine_id}/domains/{domain_id}.json
Action
Delete engineDelete an Engine by id. DELETE /api/v1/engines/{engine_id}.json
Action
Get documentRetrieve a single document by external_id from a document type. GET /api/v1/engines/{engine_id}/document_types/{document_type}/documents/{external_id}.json
Action
Get engineRetrieve a single Engine by id or name. GET /api/v1/engines/{engine_id}.json
Action
List documentsList documents within a document type/engine. GET /api/v1/engines/{engine_id}/document_types/{document_type}/documents.json
Action
List domainsList crawler domains configured on an Engine. GET /api/v1/engines/{engine_id}/domains.json
Action
List enginesList all Engines for the account. GET /api/v1/engines.json
Action
Recrawl domainTrigger a recrawl of a domain's crawled content. PUT /api/v1/engines/{engine_id}/domains/{domain_id}/recrawl.json
Action
Search documentsPerform full-text search over documents within an Engine. GET/POST https://search-api.swiftype.com/api/v1/public/engines/search.json with engine_key + q. Returns matching records grouped by document type.
Action
Update documentUpdate fields on an existing document. PUT /api/v1/engines/{engine_id}/document_types/{document_type}/documents/{document_id}/update_fields.json
Trigger
New PushPolling trigger: fires for each new push received, ordered by modified time.
Action
Create DeviceCreate a new device on your Pushbullet account.
Action
Create Pushsend a push (note, link, or file)
Action
Create SubscriptionSubscribe to a channel by its channel tag.
Action
Delete All Pushesdelete all pushes
Action
Delete ChatDelete a chat by iden.
Action
Delete DeviceDelete a device by iden.
Action
Delete PushDelete a push by iden.
Action
Delete SubscriptionUnsubscribe from a channel by subscription iden.
Action
Get Channel InfoGet information about a channel by its tag.
Action
Get Current UserGet information about the authenticated Pushbullet user.
Action
List ChatsList the chats (people you've pushed to) on your account.
Action
List DevicesList the devices on your Pushbullet account.
Action
List PushesList pushes, optionally only active and modified after a timestamp.
Action
List SubscriptionsList the channels you are subscribed to.
Action
Request File Uploadrequest authorization to upload a file
Action
Send a LinkPush a link (title + body + url) to a device, email, channel, or all your devices.
Action
Send a NotePush a note (title + body) to a device, email, channel, or all your devices.
Action
Update Chatupdate a chat (mute)
Action
Update Deviceupdate a device
Action
Update PushMark a push as dismissed.
Action
Update Subscriptionupdate a subscription (mute)
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.