5

API

Last Update 17 ngày trước

Add new profile to existing campaign via API Getting started with Teamfluence API How to setup webhooks Update existing lead via API API: fetching teamspace feed updates

How to setup webhooks

Valentine

Last Update 8 tháng trước

You can use preconfigured webhooks to tell Teamfluence when to update your system or a service on recent changes. It can be status change in connection request from the campaign or newly clipped post from LinkedIn.

Webhooks support any external URLs that accept POST data via HTTP requests. Such automation pipeline can be easily built with external providers like Make.com, Zapier or n8n. But you can also configure your own server for the same purpose.
Note: This feature is available to all paid plan subscribers.

Available events

  • Lead harvest
    • New lead created
    • Lead moved to “Qualified” stage
    • Lead updated with new signal (e.g. event or team interaction)
  • Connection campaigns
    • Connection campaign request sent
    • Connection campaign request accepted
    • Connection campaign request ignored (see Connect campaign setting in “Manage” menu)
    • Connection campaign request timed-out.
  • New clipped post
  • New contact saved
  • New profile visit


Here is the list of events available in the first release of this feature. If you didn’t find one you’re interested in, feel free to create new feature request here.

Configuring a Webhook

1. Start new pipeline / scenario with “Webhook” entry block.

Example of obtaining a webhook URL from make.com

Once you’ve got a custom webhook URL on hands, go to your Teamspace settings → Webhooks page and click on “Add” button.

You’ll see a simple submission form, where you need to specify newly obtained webhook URL and select the trigger event, which will contain related data.

Once saved you can send a sample data over to a specified webhook URL to test the connection.

Find “Test Run” button in the context menu.

On make.com we can use “Redetermine data structure” button to wait for another Teamfuence webhook call and once received, you can pass it along to any destination available. In this example we are going to send the data to Hubspot and update existing object there.

On the screenshot above we have field called crm_id which will be empty if you connection campaign list was built from search results. But for those who extended campaign through our API , this field will be carrying the same initially specified value from your own system.

Sample data

  • New clipped post
  • New contact saved
  • New profile visit
  • Connection campaign request sent
  • Connection campaign request accepted
  • Connection campaign request ignored
  • Connection campaign request timed-out.
  • New lead created / Lead Qualified / Lead updated 
Got any questions? Feel free to submit a ticket in our Help center.

Was this article helpful?

0 out of 0 liked this article

Still need help? Message Us