Zapier

Zapier yana haɗuwa da Quire ta REST API iri ɗaya, abokan OAuth da webhooks da kowane haɗin kai ke amfani da su. Babu wata lambar musamman ta Quire a kowane ɓangare; duk abin da jagorar API ta bayar, Zap ma zai iya yi.

Fara Zap idan wani abu ya faru a Quire

1. A Zapier, zaɓi Webhooks by Zapier a matsayin mai farawa, tare da taron Catch Raw Hook. Zaɓi Raw ne domin ana lissafa sa hannun bisa ainihin bytes ɗin da Quire ya aika. Kwafi adireshin da Zapier ya ba ka.
2. A Quire, buɗe /admin/webhooks, zaɓi Ƙara rajista, manna adireshin, sannan zaɓi tarurruka, misali course_completion.changed. Quire zai fara aika taron gwaji; rajistar za ta fara bayan Zapier ya karɓe shi.
3. Ƙara matakin Code by Zapier da ke tantance sa hannu ta amfani da sirrin rajista, kamar yadda aka nuna a jagorar masu haɓakawa. Dakatar da Zap idan bai inganta ba.
4. Fassara jikin saƙo sannan ci gaba da matakan da kake buƙata.

Aiki a Quire daga Zap

Yi amfani da Webhooks by Zapier tare da aikin Custom Request, ko API Request a matakin manhaja:

• URL: https://acme.quirelms.com/api/v1/..., misali /api/v1/enrolments domin shigar da mutum.
• Headers: Authorization: Bearer qk_live_... tare da maɓalli da aka ƙirƙira a /admin/integrations/api-keys don wannan Zap kaɗai, da Idempotency-Key da aka gina daga ID na mai farawa, domin sake kunna Zap daga Zapier ba zai sake shigar da mutum ɗaya ba.
• Data: JSON, kamar yadda jagorar API ta bayyana.

Domin aiki a matsayin mutum maimakon ƙungiya, yi rajistar abokin OAuth a /admin/integrations/oauth-clients da adireshin komawa na Zapier, sannan ka yi amfani da shi daga haɗin kai na Zapier mai zaman kansa.

Misali: shigar da abokin ciniki idan an kammala ciniki

1. Mai farawa: taron CRM ɗinka na “an samu nasarar ciniki”.
2. Buƙata ta musamman PUT /api/v1/users/ext:{customer id} tare da sunan mutum da imel: tana ƙirƙirar mai amfani, ko sabunta shi idan ya riga ya wanzu.
3. Buƙata ta musamman POST /api/v1/enrolments tare da mai amfani da kwas, da Idempotency-Key: deal-{deal id}.